Dynamically adjusting uav flight operations based on radio frequency signal data

ABSTRACT

In some implementations, a UAV flight system can dynamically adjust UAV flight operations based on radio frequency (RF) signal data. For example, the flight system can determine an initial flight plan for inspecting a RF transmitter and configure a UAV to perform an aerial inspection of the RF transmitter. Once airborne, the UAV can collect RF signal data and the flight system can automatically adjust the flight plan to avoid RF signal interference and/or damage to the UAV based on the collected RF signal data. In some implementations, the UAV can collect RF signal data and generate a three-dimensional received signal strength map that describes the received signal strength at various locations within a volumetric area around the RF transmitter. In some implementations, the UAV can collect RF signal data and determine whether a RF signal transmitter is properly aligned.

CLAIM OF BENEFIT TO PRIOR APPLICATIONS

This application claims priority to U.S. Provisional Application Ser.No. 62/357,294, filed Jun. 30, 2016, the contents of which isincorporated by reference herein in its entirety.

TECHNICAL FIELD

The disclosure generally relates to automatically piloting unmannedaerial vehicles.

BACKGROUND

Unmanned aerial vehicles (UAVs) are becoming more widely used to performtasks that are typically done by teams of people. For example, UAVs areused for inspecting buildings, crops, erosion of rivers and coastlines,delivery of goods, and many other tasks. A task that UAVs might beparticularly useful for is inspection of tall and/or dangerousstructures. For example, a UAV might be particularly well-suited forinspecting (e.g., taking photographs and/or other sensor data) radiotowers, RF transmitter towers, and other tall objects that are difficultfor people to inspect without risking human life. However, UAV's canoften be expensive and damaging a UAV during an inspection mission cancost the UAV operator a lot of money in repairs and lost flight time.

SUMMARY

In some implementations, a UAV flight system can dynamically adjust UAVflight operations based on radio frequency (RF) signal data. Forexample, the flight system can determine an initial flight plan forinspecting a RF transmitter and configure a UAV to perform an aerialinspection of the RF transmitter. Once airborne, the UAV can collect RFsignal data and the flight system can automatically adjust the flightplan to avoid RF signal interference and/or damage to the UAV based onthe collected RF signal data. In some implementations, the UAV cancollect RF signal data and generate a three-dimensional received signalstrength map that describes the received signal strength at variouslocations within a volumetric area around the RF transmitter. In someimplementations, the UAV can collect RF signal data and determinewhether a RF signal transmitter is properly aligned.

Implementations described herein provide at least the followingadvantages. A UAV can perform inspections of dangerous objects withoutrisking human life. The UAV can automatically avoid damage to the UAV bydeviating from an initial flight plan to avoid areas of high RF signalstrength. The UAV can collect sensor data that allows the UAV operatorto inspect the configuration and/or alignment of a RF transmitter.

The details of one or more embodiments of the subject matter of thisspecification are set forth in the accompanying drawings and thedescription below. Other features, aspects, and advantages of thesubject matter will become apparent from the description, the drawings,and the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of an example UAV flight system.

FIG. 2 is a block diagram of an example flight system for dynamicallyadjusting UAV flight operations based on radio frequency signal data.

FIG. 3 is an illustration of an example columnar flight plan generatedby flight planning system for inspecting a target object.

FIG. 4 is an illustration of an example layered flight plan generated byflight planning system for inspecting a target object.

FIG. 5 is an illustration of an initial flight plan generated based on atarget definition and/or map data as described above.

FIG. 6 is an illustration of a modified flight plan generated based onan aerial survey of the area around a target object.

FIG. 7 illustrates an example flight path for inspecting the alignmentof RF transmitters.

FIG. 8 is a flow diagram of an example process for generating a flightplan for inspecting an RF transmitter tower.

FIG. 9 is a flow diagram of an example process for executing a flightplan for inspecting an RF transmitter tower.

FIG. 10 illustrates a block diagram of an example unmanned aerialvehicle (UAV) architecture for implementing the features and processesdescribed herein.

FIG. 11A and FIG. 11B show example system architectures for thecomputing devices performing the various operations, processes, andfunctions described herein.

Like reference numbers and designations in the various drawings indicatelike elements.

DETAILED DESCRIPTION System Overview

FIG. 1 is a block diagram of an example unmanned aerial vehicle (UAV)flight system 100. For example, UAV flight system 100 can be a system ofvarious computing devices, databases, and UAVs that include hardware andsoftware configured to perform, control, and manage UAV flightoperations. System 100 can be configured, as needed, to performmission-specific flight operations in support of a mission-specificgoal, such as aerial inspection and/or aerial delivery.

In some implementations, system 100 can include flight planning system102. For example, flight planning system 102 can be a system of one ormore computers, and/or software executing on a system of one or morecomputers for planning and/or controlling the operation of one or moreunmanned aerial vehicles. Flight planning system 102 can be a system ofone or more processors, graphics processors, logic circuits, analogcircuits, associated volatile and/or non-volatile memory, associatedinput/output data ports, power ports, etc., and/or one or more softwareprocessing executing one or more processors or computers. The flightplanning system 102 may receive, store, generate, and maintain flightoperation information associated with a UAV, UAV operators and/or UAVmissions using various software modules (e.g., modules 104-112).

In some implementations, flight planning system 102 can include clientinterface module 104. For example, client interface module 104 canprovide client interfaces for UAV operators to interact with flightplanning system 102. The UAV operator can, for example, interact withclient software application 142 on user device 140 (e.g., a laptopcomputer, desktop computer, tablet computer, etc.) to connect to clientinterface module 104 of flight planning system 102 through network 170to register with flight planning system 102, to submit flight requestsand/or mission requests, and/or to receive flight packages, includingmission-specific flight plans and/or UAV programming.

For example, network 180 can be a wide area network, local area network,wireless network, cellular network, and/or the Internet. Network 180 canbe a peer-to-peer (e.g., ad-hoc) network implemented using near fieldcommunication technologies such as Bluetooth, peer-to-peer Wi-Fi, and/orother wireless peer-to-peer networking technologies. In someimplementations, network 180 can represent a wired peer-to-peerconnection, such as a universal serial bus (USB) connection between thedevices connected to network 180. For example, flight planning system102, user device 140, or ground control system 150 may connect to one ormore UAVs 160 through network 180 using a wired (e.g., USB, Ethernet,etc.) or wireless (e.g., Wi-Fi, Bluetooth, etc.) connection to configureor program the UAVs 160 to fly a mission, as described further below.Flight planning system 102, user device 140, and/or ground controlsystem 150 may connect to each other through network 180 using a wired(e.g., USB, Ethernet, etc.) or wireless (e.g., Wi-Fi, Bluetooth, etc.)connection to exchange mission requests, flight approvals, flightpackages, and/or other information, as described further below.

In some implementations, client application 142 can be a web browser andclient interface module 112 can be a web server. For example, clientinterface module 112 can send web client user interfaces (e.g., webpages, HTML, JavaScript, etc.) to client application 142 so that the UAVoperator can enter information into the web client interfaces describingthe UAV operator, the UAV operated by the UAV operator, and/or themission the UAV operator would like to fly.

In some implementations, client application 142 can be a native client(e.g., built specifically for the operating system or hardwareconfiguration of user device 140) and client interface module 112 can bea server that exchanges data with client application 142 using standardnetwork protocols. For example, client application 142 can establish acommunication session with so that the UAV operator can enterinformation into a graphical user interface of client application 142describing the UAV operator, the UAV operated by the UAV operator,and/or the mission the UAV operator would like to fly and clientapplication 142 can send the information to client interface module 104for processing by flight planning system 102.

In some implementations, flight planning system 102 can includeregistration module 106. For example, before a UAV operator can fly aUAV mission using flight system 100, a UAV operator can register withflight planning system 102 through registration module 106. For example,when the UAV operator registers with flight planning system 102 usingclient application 142, the UAV operator can provide input to clientapplication 142 describing UAV operator information, including anidentifier for the UAV operator (e.g., a company identifier, a pilotidentifier, etc.), licensing information (e.g., UAV pilot's license orcertification), contact information (e.g., contact person, telephonenumber, address, etc.), and/or any flight restrictions for the UAVoperator (e.g., regional restrictions, UAV size restrictions, UAV typerestrictions, altitude restrictions, etc.). In some implementations, theUAV operator information can include identification (e.g., registrationnumber, make, model, serial number, type, etc.) of each the UAVs thatthe UAV operator intends to fly. Client application 142 can send the UAVoperator information to registration module 106 (e.g., through clientinterface module 104). Upon receipt of the UAV operator information,registration module 106 can store the UAV operator information inoperator database 120. The UAV operator information stored in UAVoperator database 120 may include different or additional UAV operatorinformation, as may be described herein below.

In some implementations, flight planning system 102 (e.g., registrationmodule 106) can store UAV information in UAV database 122. For example,UAV database 122 can include records for each UAV operated (e.g., flown)by system 100. UAV database 122 can be populated with UAV informationprovided by UAV operators (e.g., during registration) using clientapplication 142 and client interface module 104, for example.

In some implementations, UAV configuration database 122 can be populatedby flight planning system 102 based on data received from UAVmanufacturers and/or various network resources (e.g., manufacturer'sservers, UAV operator servers, etc.) For example, when a UAV operatorsubmits a registration request, a mission request, or a flight requestto flight planning system 102, the UAV operator can identify one or moreUAVs that will be used to perform flight missions. Flight planningsystem 102 can obtain (e.g., from network resources, from the UAVoperator, etc.) the specifications for the identified UAV and store theUAV specifications in UAV database 122. A UAV record in UAV database 122can include an identifier for the UAV. For example, the UAV identifiercan be a registration number assigned to the UAV by a governmentalagency (e.g., the Federal Aviation Administration) or an identifierassigned to the UAV by flight planning system 102. The UAV record caninclude information describing the specifications of the UAV, such asmake, model, serial number, configuration type (e.g., multirotor, fixedwing, etc.), weight, payload capacity, top speed, maximum altitude,maximum range, contingency features (e.g., parachute) and/or other UAVspecifications, as may be described herein.

In some implementations, flight planning system 102 can include missionplanning module 108. For example, mission planning module 108 candetermine mission parameters, including flight plans and/or othermission parameters, based on mission requests (e.g., flight requests)submitted by a UAV operator through client interface module 104 usingclient application 142. For example, the mission parameters specified inthe mission request can include the type of mission (e.g., inspection,delivery), the target of the mission (e.g., a specific building,location, infrastructure element, natural feature, etc.), a flight plan,a description of the UAV performing the mission, and/or other missionparameters. When the mission parameters are received, flight planningsystem 102 can store the mission parameters in mission database 124.

In some implementations, mission planning module 108 can generatemission parameters based on a received mission request. For example,while a mission request submitted by a UAV operator may include a fulldefinition of the mission parameters for the requested mission (e.g.,type of mission, mission target, flight plan, UAV designation, etc.),some mission requests may not include full definition of the missionparameters required for the requested mission. For example, some missionrequests may only define the type of mission and the mission target.When a mission request does not provide a full definition of the missionparameters for the mission, mission planning module 108 canautomatically determine the missing mission parameters for the mission.For example, when the UAV operator provides a mission request that onlyidentifies the mission type, mission target, mission timeframe, and UAVdesignation, mission planning module 108 can automatically determine aflight plan that will allow the designated UAV to perform the identifiedmission type with respect to the mission target in the identifiedmission timeframe. For example, if the mission type is an inspectionmission, mission planning module 108 can determine a flight path thatallows the UAV to inspect the mission target (e.g., a building) withinthe identified mission timeframe. For example, if the mission type is adelivery mission, mission planning module 108 can determine a flightpath that allows the UAV to make a delivery to the mission target (e.g.,address) within the identified mission timeframe.

In some implementations, mission planning module 108 can automaticallydetermine flight paths for requested missions based on data stored inmap database 126. For example, map database 126 can include map data,including geospatial descriptions (e.g., location, configuration, size,dimensions, height, layout, etc.) of objects that might be the subjectof a UAV mission. For example, the objects may include natural features(e.g., geological features, geographical features, etc.) and/or man-madefeatures (e.g., buildings, pipelines, bridges, radio towers, RFtransmitter towers, etc.). Mission planning module 108 can use the mapdata to determine flight paths for inspecting the objects described bythe map data, making a delivery to the objects described by the mapdata, and/or avoiding the objects described by the map data so that theUAV does not crash into the objects while in flight.

In some implementations, the map data stored in map database 126 can bereceived from UAV operators in mission requests. For example, when a UAVoperator submits a mission request to mission planning module 108, therequest can include map data describing the target of the requestedmission. Mission planning module 108 can store the received map data inmap database 126. Alternatively, mission planning module 108 can obtainthe map data for the object identified as the mission target in amission request from one or more network resources (e.g., variousInternet services, a map vendor, etc.). Mission planning module 108 canstore the obtained map data in map database 126.

In some implementations, mission planning module 108 can store themission parameters for each flight mission request in mission database124. For example, the mission parameters can include an identifier for aUAV performing the mission. If additional information about a UAV isneeded, mission planning module 108 can look up UAV specifications andother data for the identified UAV in UAV database 122. The missionparameters can include an identifier for the UAV operator controllingthe mission. If additional information about a UAV operator is needed,mission planning module 108 can look up the UAV operator information andother data for the identified UAV operator in operator database 120.

In some implementations, the mission parameters can include a flightplan. The flight plan can be defined by a UAV operator or automaticallydetermined by mission planning module 108, as described above. Forexample, the flight plan can include a flight schedule that defines astart time (e.g., date and time), an end time (e.g., date and time),and/or a duration for the mission. The flight plan can include a flightpath for each mission. For example, the flight path can include atake-off location, a landing location, and waypoints (e.g., geospatiallocations, including latitude, longitude, altitude) for navigatingbetween the take-off location and the landing location.

The flight plan can include one or more geofences that define geospatialareas that the UAV must stay within or stay outside of when flying themission. For example, the flight plan can include a first geofence thatdefines a geospatial area (e.g., approved airspace) that the UAV muststay within while conducting the mission. The first geofence can, forexample, define a geospatial area that contains the take-off location,landing location, and all waypoints defined for the flight plan. Theflight plan can include a second geofence that defines a geospatial area(e.g., restricted airspace) that the UAV must not go within. Forexample, the second geofence can be generated to keep the UAV out ofpopulated areas, military installations, and/or other protected areas(e.g., fuel storage sites, nuclear reactors, etc.).

The flight plan can include contingency data for the mission. Forexample, the contingency data can define contingency events (e.g., motorfailure, control failure, deviation from flight path, exiting geofence,etc.) and maneuvers to perform in response to a detected contingencyevent (e.g., fly to emergency landing zones, follow emergency flightpaths, deploy parachute, etc.).

In some implementations, the mission parameters can describe specialpayloads for the UAV to perform the mission. For example, the UAVoperator can define special UAV payloads required for performing the UAVmission in the mission request received by mission planning module 108.For example, special payloads can include cameras, sensors, payloadcarrying apparatus, etc., configured on the UAV for performing aspecific mission. For example, if the UAV mission is to perform a visualinspection of a natural disaster, then the special payload may include ahigh definition camera for taking pictures of the natural disaster. Ifthe UAV mission is to detect thermal emissions, electromagneticemissions, gas leaks, or other types of thermal, radiological, orchemical leaks, the special payload can include sensors for detectingthermal, radiological, or chemical leaks.

In some implementations, after determining the mission parameters for amission request and storing the mission parameters in mission database124, mission planning module 108 can determine whether the missionparameters conflict with other pending missions in mission database 124.For example, flight planning system 102 can be configured to manage theairspace needed for UAV missions. Therefore, after mission planningmodule 108 determines a flight plan for a requested mission, missionplanning module 108 can determine whether the schedule for the requestedmission conflicts with other flight missions that have flight plans inthe same airspace at the same time as the requested mission. If no othermissions are scheduled at the same time and same airspace as therequested mission, then mission planning module 108 can authorize therequested mission, reserve the necessary airspace, and indicate in themission record in mission database 124 that the requested mission isapproved and/or scheduled. If another mission is scheduled at the sametime and same airspace as the requested mission, then mission planningmodule 108 can notify the requesting UAV operator (e.g., through clientapplication 142) that the airspace needed for the requested mission isunavailable (e.g., has already been reserved) at the requested time andindicate in the mission record in mission database 124 that therequested mission is not approved and/or not scheduled. The UAV operatorcan then request an alternative time for the mission until anappropriate time for the requested mission is determined.

In some implementations, flight planning system 102 can include flightpackage module 112. For example, after mission planning module 108determines the mission parameters for a received mission request andapproves the requested mission, mission planning module 108 can send themission parameters to flight package module 112 for packaging intoflight package 170 for delivery to ground control system 150 and/or UAVs160. For example, flight package 170 can include one or more flightplans. Each flight plan can include a flight schedule (e.g., start time,end time), start location, destination location, waypoints fornavigating from the start location to the destination location,contingency event definitions, contingency operations for eachcontingency event. Flight package 170 can include operator (e.g., pilot)information, such as the name of the operator, the operator's employer,the operator's license information (e.g., including UAV ratings), etc.Flight package 170 can include UAV information, such as the UAV type,payload, model, size, operating range, and/or other UAV specificationsdescribing the UAV that will perform the mission described by the flightpackage. For example, a UAV operator can use UAV controller application152 on ground control system 150 to program and/or control one or moreUAVs 160 according to the data in flight package 170. Alternatively,flight planning system 102 can send flight package 170 directly to oneor more UAVs 160 to program the UAVs 160 according to the flight package170. UAVs 160 can then, in some implementations, automatically pilotthemselves according to the flight plans and/or other data in flightpackage 170.

In some implementations, system 100 can include one or more UAVs 160.For example, UAV 160 can include mission module 162. For example,mission module 162 can process flight package 170 to determine themission parameters for a scheduled mission or flight, including theflight plan, contingency conditions (e.g., events that trigger acontingency maneuver), and/or contingency maneuvers for the mission.Mission module 162 can, for example, determine the flight plan for themission based on the flight plan data in flight package 170. Missionmodule 162 can send the flight plan (e.g., start location, waypoints,etc.) to flight control module 164.

In some implementations, UAV 160 can include flight control module 164.For example, flight control module 164 can use the flight plan data tocause UAV 160 to automatically navigate from a take-off location, to oneor more waypoints, and to the landing location defined by the flightplan automatically based on data provided by various motion sensorsand/or location subsystems of the UAV. For example, flight controlmodule 164 can determine the current location of UAV 160 based onvarious wireless signals (e.g., global navigational satellite signals,radio access technology signals, Wi-Fi signals, etc.) and motion sensordata. Flight control module 164 can use the wireless signals and/ormotion sensor data to determine the location of UAV 160 using well-knowndead reckoning and/or trilateration techniques, for example. Flightcontrol module 164 can compare the current location of UAV 160 to thelocation of the next waypoint in the flight plan received from missionmodule 166 to determine a heading along which UAV 160 should fly inorder to reach the next waypoint. Flight control module 164 can performthis process periodically while in flight to adjust the heading of UAV160 so that UAV 160 can travel to the next waypoint. For example, if UAV160 is flying in an environment with a strong wind, flight controlmodule 164 may need to adjust the heading of UAV 160 many times as it isblown around by the wind in order to reach the next waypoint.

In some implementations, mission module 162 can determine thecontingency information for the mission based on the contingencyconditions and corresponding contingency maneuvers defined in flightpackage 170. For example, each contingency event can be associated witha respective contingency maneuver that may be different than thecontingency maneuvers for other contingency events. Some contingencyconditions can be associated with the same contingency maneuver. Forexample, flight package 170 can describe a default contingency maneuver(e.g., land in designated safe zone) that can be triggered by multiplecontingency events. Mission module 162 can send the contingencyinformation to contingency module 166 so that contingency module 166 canmonitor for contingency events and cause UAV 160 to execute contingencymaneuvers.

In some implementations, UAV 160 can include contingency module 166. Forexample, contingency module 166 can receive contingency information frommission module 162. The contingency information can, for example,include geofence definitions for approved airspace and restrictedairspace and contingency maneuvers to perform when UAV 160 exitsapproved airspace or enters restricted airspace. For example,contingency module 166 can use the current location of UAV 160 toautomatically keep UAV 160 within approved airspace. For example,contingency module 166 can use the current location information todetermine when UAV 160 exits a geofence that defines approved airspace.Contingency module 166 can use the current location of UAV 160 todetermine when UAV 160 enters a geofence that defines restrictedairspace, as described above.

In some implementations, when contingency module 166 detects acontingency event, contingency module 166 can automatically initiate acontingency maneuver. The contingency maneuver can be defined by flightpackage 170. The contingency maneuver can be a default contingencymaneuver configured in contingency module 166. For example, whencontingency module 166 detects that UAV 160 exits a geofence definingapproved airspace (e.g., a contingency event) for the mission and/orwhen contingency module 166 detects that UAV 160 enters a geofencedefining restricted airspace (e.g., a contingency event), thecontingency module 166 can initiate a contingency maneuver. For example,contingency module 166 can send contingency maneuver data to flightcontrol module 162 to cause flight control module 164 to execute acontingency maneuver. For example, the contingency maneuver data candefine a flight path for returning UAV 160 to an approved flight path,the contingency maneuver data can define a flight path to safely landUAV 160 at a location where UAV 160 can be safely recovered by the UAVoperator, the contingency maneuver data can indicate that flight controlmodule 162 should deploy a parachute, or perform some other contingencymaneuver.

In some implementations, flight planning system 102 can include missiontelemetry module 112. For example, mission telemetry module 112 canreceive mission operational information, including aircraft operationaldata and/or mission-specific data collected and/or generated by UAVs 160while performing a UAV mission. In some implementations, aircraftoperational data can include the UAV's operational information, such asthe UAV's precise three-dimensional location in space, velocityinformation, UAV status (e.g., health of components included in theUAV), executed contingency plans, and so on. Thus, the missionoperational information can include a flight data log that storeschanges in the aircraft operational data over time. In someimplementations, the mission-specific data can include data generated byspecial or mission specific payload devices affixed to the UAV. Forexample, the mission-specific data can include still images, videofeeds, sensor data, and/or other mission-specific data generated wheninspecting a mission target and/or making a delivery to the missiontarget, as described above. When mission telemetry module 112 receivesmission operational information, mission telemetry module 112 can storethe mission operational information in operational database 128. Forexample, operational database 128 can include a record of each UAVmission managed by flight planning system 102, including the missionoperational data received for each respective mission.

In some implementations, the ground control system (GCS) 150 may act asa user device for interacting with the flight planning system 102. Forexample, GCS 150 can include the functionality and features of userdevice 140. GCS 150 can be configured to communicate with and control(e.g., using UAV controller application 152) one or more UAVs 160 whilethe UAVs are in flight. For example, UAV controller application 152 canreceive information from flight planning system 102 describing a UAV'sflight through reserved airspace. For example, flight planning system102 can receive (e.g., real-time) UAV location information and transmitthe information to UAV controller application 152. UAV controllerapplication 152 can present on a display of GCS 150 a time-basedgraphical representation of a flight through the reserved airspace basedon the information received from flight planning system 102. A UAVoperator can provide input to a graphical user interface of UAVcontroller application 152 to make adjustments to the UAV's flight inreal-time. For example, the UAV operator may notice a problem with theaircraft or an obstruction in the airspace where the UAV is flying andcommand the UAV to initiate a contingency maneuver to safely land and/oravoid the obstruction in the airspace. Thus, UAVs may automaticallypilot themselves based on the data in flight package 170 and/or the UAVoperator may manually control UAVs 160 using UAV controller application152 on GCS 150.

FIG. 2 is a block diagram of an example flight system 200 fordynamically adjusting UAV flight operations based on radio frequencysignal data. For example, system 200 can correspond to system 100 ofFIG. 1. System 200 can be configured, for example, to fly UAV missionsto inspect radio transmitters (e.g., or transceivers) mounted on masts,towers, or other tall objects. For example, a radio transmitter maygenerate and/or transmit radio signals that may cause damage toelectronics, biological organisms (e.g., humans, pets, livestock, etc.),and/or other devices, objects, etc. For example, high power radiotransmitters (e.g., microwave transmitters) are commonly used intelephonic communication systems, wireless data communication systems,and/or other types of communication systems.

It is essential that the RF transmitters operate properly and areproperly aligned so that these high power transmitters can operateefficiently and avoid transmitting signals to locations that might causedamage to life, critical electronics, and/or infrastructure. Routineinspections and maintenance of these RF transmitters allowmanufacturers/operators to make repairs or adjustments according to amanaged timeline and avoid unscheduled shutdowns that may cost themanufacturer a large sum of money.

Typically, inspections and/or alignment of RF transmitters are performedby humans on the ground or on other RF transmitter towers usingsignaling devices to inspect the components of the RF transmitters andcheck the alignment of the transmitters. However, ground inspections areoften do not provide a clear picture of the transmitted signal patternsand tower to tower alignment using signaling devices (e.g., beams oflight) are inaccurate.

UAVs provide an opportunity for the manufacturer to inspect the towermounted RF transmitters at relatively close range without incurring thecost of shutting down the RF transmitters. Additionally, UAVs can beconfigured with sensors that allow the UAV to capture optical images ofthe RF transmitter in addition to determining the received signalstrength at various locations around the RF transmitter. However, UAVscan be susceptible to damage caused by the powerful RF signals generatedby these RF transmitters. Thus, UAV flight system 200 can providefeatures and functionality that allow UAVs to avoid RF signal damagewhile improving the quality of RF transmitter inspections andalignments.

In some implementations, flight system 200 can include user device 140.As described above, user device 140 can include client application 142.A UAV operator can interact with client application 142 to generate andsubmit a UAV mission request as described above. For example, the UAVoperator can interact with client application 142 to generate RFtransmitter inspection mission request 202. The UAV operator can, forexample, provide input to client application 142 defining the missionparameters specified in mission request 202, as described further below.

In some implementations, mission request 142 can specify missionparameters for the RF transmitter inspection mission. For example, themission parameters can include an inspection target definition thatdefines or describes the object (e.g., RF transmitter tower, targetobject, etc.) to be inspected. The target definition can, for example,include a geographical location of the target. For example, thegeographical location can correspond to the center of the object (e.g.,the center of the RF transmitter). The target definition can include thedimensions of the target object. For example, the dimensions can includethe height, width, radius, diameter, etc., of the target object. Thetarget definition can, for example, include any other informationrequired to generate a three-dimensional model (e.g., a 3D point cloud,digital surface model, surface mesh, etc.) of the target object. Thetarget definition can include location data for points of interest onthe target object. For example, the target definition can includecoordinates, relative location data, etc., that identifies points ofinterest on the surface of the target object. For example, the points ofinterest can correspond to various RF signal transmitters mounted on atower (e.g., cellular tower, radio tower, microwave transmitter tower,etc.)

Alternatively, the target definition can identify sections or areas ofthe target object to inspect. For example, the target definition canindicate that the entire target object is to be inspected or aparticular portion (e.g., less than all) of the target object is to beinspected. In the case of RF transmitter tower, the points of interestcan include the section of the tower where the RF transmitters aremounted, critical portions of the support structure, the top half of theRF transmitter tower, and the like. The target definition can include adescription of obstructions (e.g., guy lines, bracing, etc.). The targetdefinition can include a description of outbuildings, cableinstallations, and/or other structures in the vicinity of the RFtransmitter tower.

In some implementations, the target definition can be generated by theUAV operator, as described above. For example, the target definition candefine the physical dimensions of the target object (e.g., the RFtransmitter tower, RF transmitter, etc.), as described above. The targetdefinition can define the radio frequencies to be mapped or inspected.Alternatively, the target definition can be obtained by user device 140or flight planning system 102 from the manufacturer or operator of theRF transmitter tower. For example, a RF transmitter manufacturer and/ortower operator can provide frequency and power output information foreach RF transmitter mounted on a tower. The RF transmitter manufacturerand/or tower operator can, for example, provide RSSI maps that indicatethe expected RSSI for a transmitted frequency at different locationsaround the transmitter tower. For example, the UAV operator can provideinput to client application 142 identifying the target object and/or thelocation of the target object (e.g., the RF transmitter tower), andclient application 142 or flight planning system 102 can obtain thetarget definition from a server or other computing device associatedwith the manufacturer or operator of the RF transmitter tower based onthe object identifier and/or location.

In some implementations, the mission parameters specified in missionrequest 204 can include no-fly zones for the target object. For example,the no-fly zones (e.g., geospatial or volumetric areas) can be specifiedin the target definition obtained from the RF transmitter towermanufacturer, as described above. The no-fly zones can be automaticallygenerated by client application 142 and/or flight planning system 102based on the obstructions identified in the target definition describedabove. The no-fly zones can be specified by the UAV operator byproviding input describing the no-fly zones. For example, the UAVoperator can provide input to a graphical user interface (e.g., a mapdisplay) of client application 142 that defines the no-fly zones in thevicinity of the target object (e.g., the RF transmitter tower).

In some implementations, the mission parameters specified in missionrequest 204 can include inspection parameters. For example, theinspection parameters can include specifications for the various sensorsto be used on the UAV when conducting the aerial inspection of thetarget object (e.g., the RF transmitter tower). The inspectionparameters can include specifications for an optical digital camera(e.g., optical imaging sensor 224), including the camera sensor size(e.g., megapixels), resolution, and/or the focal length of the camera.If the camera has an adjustable focal length (e.g., a zoom lens), thenthe focal length can include maximum and minimum focal length values forthe camera.

In some implementations, the inspection parameters can define thesurface sampling distance required for conducting an optical or visualinspection. The surface sampling distance can, for example, be similarto ground sampling distance in that the surface sampling distancedefines the amount of surface area that should be covered by a singlepixel of the cameras described above (e.g., 1 mm per pixel, 3 mm perpixel, etc.). For example, flight planning system 102, GCS 150, and/orUAV 220 can use the required surface sampling distance, the camerasensor size (or resolution), and the focal length of the camera, todetermine appropriate standoff distances for inspecting (e.g., capturingimages of) the target object (e.g., the RF transmitter tower). Forexample, the standoff distance defines how far away from target objectthe camera can be (or must be) to capture an image (e.g., optical)having the required surface sampling distance. If the camera has anadjustable focal length (e.g., min-max), then the standoff distance canbe defined as a range of values between a minimum and maximum distance.

The inspection parameters can include specifications for an RF signalsensor (e.g., RF signal sensor 222, RF signal sensor 223). For example,the sensor specifications can define the type of RF signal sensor andthe frequencies that the RF signal sensor is configured to detect. Forexample, the RF signal sensor can be a radio receiver configured togenerate a received signal strength indication (RSSI) for a signalreceived by the RF signal sensor. The RF signal sensor can be configuredto detect (e.g., receive) an RF signal having a particular frequency.For example, the RF signal sensor (e.g., radio frequency receiver) canbe configured with a filter that allows the RF signal sensor to receivesignals within a particular frequency band. The RF signal sensor can bea wide-band RF signal sensor that can receive signals from variousfrequencies within the frequency spectrum. For example, the RF signalsensor can be a full frequency RF signal receiver. The RF signal sensorcan be a directional or omnidirectional RF signal sensor. For example,the RF signal sensor can be coupled to a directional or omnidirectionalantenna for detecting RF signals transmitted from a specific directionor broadcast from any direction.

In some implementations, the inspection parameters can indicate the typeof inspection for the UAV to perform. For example, the inspection can bea visual inspection where the UAV captures optical images for a human toinspect. The inspection can be a RSSI survey of specified frequencies orall frequencies in the volumetric area surrounding a RF transmittertower. The inspection can be an alignment inspection to determinewhether two RF transmitters/receivers on different towers are alignedproperly.

In some implementations, the mission parameters can include a flightplan. For example, the UAV operator can provide input to clientapplication 142 to specify a take-off location (e.g., startinglocation), a landing location (e.g., an ending location), and/or one ormore waypoints for flying from the starting location to the endinglocation. For example, the waypoints can be selected to provide the UAVa vantage point from which to perform the inspection (e.g., captureimages, sensor data, etc.) of the target object.

In some implementations, after receiving the mission parameters from theUAV operator and/or other resources, client application 142 can send RFtransmitter tower inspection mission request 202, including the missionparameters, to flight planning system 102. For example, flight planningsystem 102 can receive mission request 202 and generate a flight planfor inspecting the target object (e.g., the RF transmitter tower)according to the mission parameters in mission request 202.

In some implementations, flight planning system 102 can include RFtransmitter tower inspection mission planning module 210. For example,mission planning module 210 can correspond to mission planning module108 of FIG. 1. Mission planning module 210 can plan the RF transmittertower inspection mission based on mission request 202, for example.Mission planning module 210 can generate or obtain map datacorresponding to target definition received in mission request 202. Forexample, mission planning module 210 can generate a three-dimensionalmodel or map of the target object based on the target object locationand target object dimensions information included in mission request202. Mission planning module 210 can obtain a three-dimensional model ormap of the target object from network resources (e.g., the RFtransmitter tower manufacturer's server, the RF transmitter toweroperator's server, etc.). If flight planning system 102 has previouslygenerated a flight plan for the target object, mission planning module210 can obtain a three-dimensional model or map of the target objectfrom map database 126, as described above.

In some implementations, mission planning module 210 can generate aflight plan for performing a visual or optical inspection of points ofinterest on the target object specified in mission request 202. Forexample, if the UAV operator has specified a flight plan in missionrequest 202, mission planning module 210 can confirm that theoperator-specified flight plan is suitable for inspecting the targetobject. If the UAV operator has not specified a flight plan in missionrequest 202 or the flight plan specified by the UAV operator is notsuitable for the requested mission, mission planning module 210 canautomatically generate a flight plan for inspecting the target object.For example, mission planning module 210 can generate a flight plan thatincludes a take-off location, a landing location, and one or morewaypoints that will allow UAV 220 to inspect the points of interestspecified in mission request 202 while avoiding the obstructions andno-fly zones specified in the mission request and/or map datacorresponding to the target object.

When mission request 202 specifies a portion of the target object toinspect, mission planning module 210 can automatically determine orgenerate points of interest on the target object based on the portion ofthe target object to be inspected and the sensor specificationsspecified in the mission request. For example, when the inspectionmission type is a visual inspection mission, mission planning module 210can determine points of interest on the RF transmitter tower such thatafter the camera captures an image of each point of interest, the entireportion of the target object has been captured in the images (e.g.,optical images, photographic images, thermal images, etc.) generated bythe camera. For example, mission planning module 210 can generate aflight plan that includes a take-off location, a landing location, andone or more waypoints that will allow UAV 220 to inspect the points ofinterest generated or determined by mission planning module 210 whileavoiding the obstructions and no-fly zones specified in the missionrequest and/or map data corresponding to the target object.

In some implementations, mission planning module 210 can generate aflight plan to survey the received signal strength (e.g., of a specificfrequency band, of all frequencies, etc.) at various locations aroundthe target object specified in mission request 202. For example, whenthe inspection mission type is an RSSI mapping mission, mission planningmodule 210 can generate a flight plan that includes waypoints where theUAV can generate a received signal strength indication (RSSI) indictingthe strength of the RF signal at each respective waypoint and/orlocations between waypoints. For example, after collecting or generatingRSSI values and location information indicating where the RSSI valueswere generated, UAV 220 and/or flight planning system 102 can generate athree-dimensional RSSI map that represents the RSSI at various locationsin the volumetric space surrounding the RF transmitter tower.

In some implementations, mission planning module 210 can generate aflight plan to inspect the alignment of the target object or objectsspecified in mission request 202. For example, when the inspectionmission type is a transmitter alignment mission, mission planning module210 can generate a flight plan that includes waypoints between targetobjects (e.g., between two different RF transmitters) where the UAV canreceive RF signals from each target object and determine whether thetarget objects are properly aligned. For example, after collecting RFsignal data and location information at each waypoint and/or locationsbetween waypoints, UAV 220 and/or flight planning system 102 candetermine whether the RF transmitters (e.g., microwave transmitters) oneach RF transmitter tower are properly aligned based on the originationlocation, orientation and/or overlap of the signal beams received fromeach RF transmitter.

In some implementations, mission planning module 210 can determine thewaypoints based on sensor specifications (e.g., optical cameraspecifications) and the required surface sampling distance specified inmission request 202. For example, mission planning module 210 candetermine the stand-off distance or a range of stand-off distances forcapturing images that achieve the required surface sampling distance, asspecified in mission request 202. For example the stand-off distance (orrange of stand-off distances) can be determined based on the specifiedsurface sampling distance, the size of the camera sensor, and the focallength (or lengths) of the camera using well-known techniques. After thestand-off distance (or range of distances) is determined, missionplanning module 210 can select waypoints that provide a view of thepoints of interest on the target object and that are located at adistance from their respective points of interest determined based onthe stand-off distance or range of stand-off distances, as describedfurther below.

In some implementations, mission planning module 210 can determine aflight plan based on RF signal data associated with the target object.For example, when the target object is a RF transmitter tower, missionplanning module 210 can obtain an expected RSSI map for the area aroundthe RF transmitter tower that describes the expected RSSI at differentdistances from and/or locations around the RF transmitter tower undernormal, average, or expected operating conditions. For example, the RSSImap can describe the RSSI distribution around the RF transmitter towerwhen the RF transmitter tower is operating as designed, under normalconditions, and with the proper configuration or orientation of the RFtransmitters.

In some implementations, mission planning module 210 can determine thesafe RSSI threshold for the UAV (e.g., UAV 220) specified in missionrequest 202 (e.g., based on UAV specifications stored in UAV database122). For example, a RF signal with a high RSSI value may interfere withthe radio communications of UAV 220 and/or may cause problems with theelectrical circuits that control the flight and/or data processingcomponents of UAV 220. Thus, the safe RSSI threshold value can definethe maximum RSSI value that UAV 220 can receive and still functionproperly. Mission planning module 210 can determine a minimum safeoperating distance from the RF transmitter tower based on the expectedRSSI map for the RF transmitter tower and the safe RSSI threshold forUAV 220. Mission planning module 210 can adjust the determined flightplan to keep UAV 220 at a distance greater than the minimum safeoperating distance. For example, mission planning module 210 candetermine or specify waypoints that are at a distance away from the RFtransmitter tower that is greater than the minimum safe operatingdistance.

After mission planning module 210 determines or generates the flightplan for the requested inspection mission, mission planning module 210can generate flight package 212 that includes the flight plan generatedby mission planning module 210. For example, flight package 212 caninclude the flight plan, a geofence that defines airspace reserved forthe flight plan, geofences that define no-fly zones (e.g., restrictedairspace), map data that includes a 3D model of the target object (e.g.,the RF transmitter tower), contingency event definitions andcorresponding contingency maneuvers, and any other data required forflying the requested mission, as may be described herein. For example,the contingency events for the RF transmitter tower inspection missioncan include (e.g., in addition to geofence events) an RSSI thresholdevent that causes UAV 220 to move to a safe distance to avoid RF signalinterference with the operation of UAV 220 when the RSSI value detectedby UAV 220 exceeds the safe RSSI threshold value, as described above.After generating the flight package, flight planning system 102 can sendflight package 212 to UAV controller application 152 on ground controlsystem 152 and/or to UAV 220. In some implementations, UAV controllerapplication 152 can send flight package 212 to UAV 220 to configure theUAV for the inspection mission.

In some implementations, flight system 200 can include UAV 220. Forexample, UAV 220 can correspond to UAV 160 of FIG. 1. UAV 220 caninclude mission specific hardware and/or software for performing the RFtransmitter tower inspection described above. For example, UAV 220 caninclude RF signal sensor 222 and/or RF signal sensor 223. RF signalsensor 222 and RF signal sensor 223 can be the same type of sensor. Forexample, RF signal sensor 222 and RF signal sensor 223 can bedirectional antennas pointed in different directions on UAV 220 todetect RF signals received from different directions. RF signal sensor222 and RF signal sensor 223 can be different types of RF signalsensors. For example, RF signal sensor 222 can be a RF receiver thatfilters RF signals in order to detect signals within a first frequencyband, while RF signal sensor 223 can be a RF receiver that filters RFsignals in order to detect signals within a second frequency band. RFsignal sensor 222 can be a RF receiver that filters RF signals in orderto detect signals within a first frequency band, while RF signal sensor223 can be a wide band RF receiver that detects signals of allfrequencies.

In some implementations, UAV 220 can include optical sensor 224 (e.g.,an optical imaging camera), as described above. UAV 220 can includedistance sensor 228 (e.g., LIDAR) for determining the distance betweenUAV 220 and the inspection target object (e.g., the RF transmittertower). When UAV 220 receives flight package 212 from flight planningsystem 102 or GCS 150, mission module 162 can configure UAV 220 to flythe inspection mission defined by flight package 212, as describedabove. For example, mission module 162 can send flight control 164 theflight plan so that flight control module 162 can navigation and/orcontrol UAV 220 while in flight. Mission module 162 can send contingencymodule 166 the contingency data (e.g., contingency events, contingencymaneuvers) from flight package 212 so that contingency module 166 canmonitor for contingency events and trigger contingency maneuvers asdescribed above.

FIG. 3 is an illustration of an example columnar flight plan 300generated by flight planning system 102 for inspecting a target object.For example, the flight plan can be an initial flight plan generated byflight planning system 102 for piloting UAV 220 when performing therequested RF transmitter tower inspection mission, as described above.The flight plan can include, for example, reserved airspace geofence 302defining airspace that UAV 220 must stay within while flying the RFtransmitter tower inspection mission. The flight plan can includerestricted airspace geofence 308 defining airspace around RF transmittertower 310 that UAV 220 may stay outside of while flying the RFtransmitter tower inspection mission. For example, geofence 308 can bedetermined based on the minimum safe operating distance determined byflight planning system 102, as described above.

In some implementations, the flight plan can include starting/endinglocation 350 and waypoints 320-334. For example, waypoints 320-334 canbe arranged or ordered such that when UAV 220 moves from waypoint towaypoint, UAV 220 follows a flight path that is mostly columnar. Forexample, waypoints 320-360 can be arranged in order such than UAV 220flies vertically upward from waypoint 320 to waypoint 326 in column 340.Stated differently, waypoints 320-326 can be arranged at increasingaltitudes over the same ground location (e.g., geographical location,latitude/longitude coordinates, etc.) so that UAV 220 flies upward overthe same ground location from waypoint 320 to waypoint 326 whileinspecting RF transmitter tower 310 and/or the transmitters affixedthereto.

After UAV 220 reaches waypoint 320, UAV 220 can transition to anothercolumn (e.g., column 342) where UAV 220 can navigate downward throughwaypoints 328-334 while inspecting RF transmitter tower 310. Forexample, waypoints 320-334 can be arranged so that UAV 220 can collectsensor data for the points of interest on RF transmitter tower 310specified in mission request 202. For example, while flying fromwaypoint to waypoint in flight plan 300, UAV 220 can collect images, RFsignal information, location information, etc., at various locationsalong flight path 300. Further, waypoints 320-334 can be arranged suchthat UAV 220 can avoid obstructions, such as guy lines or supportssecuring RF transmitter tower 310. While UAV 220 is flying, UAV operator370 can monitor the progress of UAV 220 using GCS 150. UAV operator 370can, for example, control UAV 220 while UAV 220 is in flight using GCS150. For example, if UAV operator 270 notices a malfunction, dangerousenvironmental conditions, or some other dangerous situation, UAVoperator 270 can initiate a contingency maneuver (e.g., return to base,land in safe zone, etc.) using GCS 150.

FIG. 4 is an illustration of an example layered flight plan 400generated by flight planning system 102 for inspecting a target object.For example, the flight plan can have the same geofences as the flightplan of FIG. 3.

In some implementations, flight planning system 102 can generate aflight plan that causes UAV to circle RF transmitter tower 310 in ahorizontal layered flight plan. For example, rather than the verticalcolumnar approach described in FIG. 3, flight planning system 102 cangenerate a flight plan such that waypoints are ordered to cause UAV 220to inspect RF transmitter tower 310 at one altitude (e.g., a first layeror level) before increasing or decreasing altitude to inspect RFtransmitter tower 310 at a different altitude (e.g., a second layer orlevel). The altitudes at which UAV 220 circles RF transmitter tower 310can be determined based on the altitudes at which points of interesthave been identified on RF transmitter tower 310, for example.

In some implementations, the flight plan can specify an order for thewaypoints that causes UAV 220 to take a bottoms up approach toinspecting RF transmitter tower 310. For example, UAV 220 can take offfrom starting location 450 and travel at the same (or about the same)altitude from waypoint 402 to waypoint 408 around RF transmitter tower310 while inspecting (e.g., capturing optical images, capturing RSSIdata, capturing RF signal data, capturing UAV location data, etc.) of RFtransmitter tower 310. When UAV 220 has circumnavigated RF transmittertower 310 or when UAV 220 reaches an obstruction or restricted airspacegeofence, UAV 220 can transition to a higher altitude (e.g., transitionto waypoint 410) and circumnavigate RF transmitter tower 310 at thehigher altitude (e.g., by navigating from waypoint 410 to waypoint 418).After transitioning to the higher altitude, UAV 220 can circumnavigateRF transmitter tower 310 in the same direction (e.g., clockwise) as theprevious altitude or in a reverse direction (e.g., counter clockwise).For example, UAV 220 may reverse direction when UAV 220 has reached anobstruction or geofence that UAV 220 cannot or should not cross.

In some implementations, the flight plan can specify a top down approachthat causes UAV 220 to travel from waypoint 418 to waypoint 402 from ahigh altitude (waypoint 418) through decreasing altitudes until reachingthe low altitude waypoint 402. For example, the flight plan can causeUAV 220 to travel in the reverse of the bottoms up approach describedabove.

FIG. 5 is an illustration of an initial flight plan 500 generated basedon a target definition and/or map data as described above. The initialflight plan can be generated by flight planning system 102 based on astatic or default target definition and/or map data and, therefore, maynot account for environmental conditions, such as wind, weather, currentoperating conditions of the RF transmitter tower, and/or othervariables.

In some implementations, flight plan 500 can include reserved airspacegeofence 502. For example, geofence 502 can define an airspace that hasbeen reserved for the aerial inspection of RF transmitter tower 310. UAV220 can be programmed to stay within geofence 502 while conductingflight operations. UAV 220 can initiate a contingency maneuver if UAV220 should stray outside of geofence 502 (e.g., UAV 220 may be pushedoutside of the geofence by a gust of wind or some other force).

In some implementations, flight plan 500 can include restricted airspacegeofence 504. For example, geofence 504 can be generated based on thelocation and dimensions of RF transmitter tower 310 and any attached RFtransmitters. For example, geofence 504 can be generated to keep UAV 220from flying to close to tower 310 so that UAV 220 does not crash intotower 310. UAV 220 can be programmed to stay outside of restrictedairspace geofence 504. For example, should UAV 220 stray into geofence504, UAV 220 can perform a contingency maneuver to quickly exit theairspace defined by geofence 504.

In some implementations, flight plan 500 can include restricted airspacegeofences 506, 507, and/or 508. For example, geofences 506, 507, and/or508 can be generated based on the maximum safe RSSI threshold for UAV220. For example, the minimum safe operating distance from tower 310 canbe determined by flight planning system 102 based on the default orstatic RSSI map data for RF transmitter tower 310 and the safe RSSIthreshold for UAV 220. For example, the safe RSSI threshold cancorrespond to the maximum RSSI value that UAV 220 can operate in withoutcausing damage to UAV 220. A single RF transmitter can generate multipleRF signal lobes representing a signal that is broadcast in differentdirections from the RF transmitter. Geofences 506, 507, and/or 508 cancorrespond to different signal lobes generated by the same transmitter,for example. Geofences 506 and 508 can correspond to side lobes.Geofence 507 can correspond to the main lobe. UAV 220 can be programmedto stay outside of restricted airspace geofences 506, 507, and/or 508.For example, should UAV 220 stray into one of geofences 506, 507, and/or508, UAV 220 can perform a contingency maneuver to quickly exit theairspace defined by geofences 506, 507, and/or 508.

In some implementations, flight plan 500 can include a minimum stand-offdistance and a maximum stand-off distance. For example, the minimum andmaximum stand-off distances can be determined based on the focal lengths(e.g., range of focal lengths) of the cameras configured on UAV 220 andthe surface sampling distance defined for the inspection mission. Forexample, minimum stand-off distance and maximum stand-off distance candefine an area in which UAV 220 can move and still capture images thatprovide the required surface sampling distance. The minimum and maximumstand-off distances allow UAV 220 to adjust its flight path to avoidobstructions and RF signal damage while still accomplishing the RFtransmitter tower inspection mission and providing images that meet therequired surface sampling distance for the mission. As illustrated byFIG. 5, the minimum standoff distance may be closer to RF transmittertower than geofences 504-508 may allow. Thus, the effective operatingarea of UAV 220 for the inspection may be defined by maximum standoffdistance and geofences 504-508 rather than by maximum standoff distanceand minimum standoff distance.

In some implementations, flight plan 500 can include a flight pathdefined by a take-off/landing location and waypoints (e.g., waypoints512-534). For example, since FIG. 5 provides a top-down view of flightplan 500, each waypoint 512-534 can represent multiple waypoints havingthe same ground location but different elevations, as illustrated inFIGS. 3 and 4. Waypoints (e.g., represented in FIG. 5 and other figuresby triangles) can be selected by flight planning system 102 based onpoints of interest determined for the inspection mission, based onrestricted airspace geofences, based on the minimum and maximumstand-off distances, and/or based on locations that provide enoughcoverage to generate a three-dimensional RSSI map of the areasurrounding RF transmitter tower 310, as described above.

When conducting a RSSI mapping inspection mission, UAV 220 can fly towaypoints laid out in concentric circles (or rings) around RFtransmitter tower 310. For example, the waypoints within each circle canbe laid out at a specified distance from each other (e.g., 3 metersbetween waypoints, 10 meters between waypoints, etc.). Thus, circlesfarther away from tower 310 may have a greater number of waypoints thancircles closer to tower 310. UAV 220 can, for example, fly from waypointto waypoint (e.g., waypoints 512, 514, 516, etc.) in ring 510 first,then to the waypoints (e.g., waypoints 522, 524) in ring 520, then tothe waypoints (e.g., waypoints 532, 534) in ring 530 while performingthe inspection of tower 310. However, since waypoint 524 is withingeofence 507, waypoint 524 may be excluded from the flight plan by UAV220 or flight planning system 102.

By following this flight plan, UAV 220 can take RSSI measurementsstarting at the waypoints most distant from RF transmitter tower 310 andgradually move to waypoints that are closer to RF transmitter tower 310.Since RSSI values for a signal transmitted from RF transmitter tower 310will typically become larger as UAV 220 moves closer to tower 310, thisapproach allows UAV 220 to detect when RSSI values exceed the maximumsafe RSSI threshold value for UAV 220 (e.g., a contingency event) andtake corrective action to avoid damage to UAV 220 (e.g., a contingencymaneuver). For example, when UAV 220 detects an RSSI value equal to orgreater than the maximum safe RSSI threshold value for UAV 220, UAV 220can initiate a contingency maneuver that causes UAV 220 to reversecourse and fly in the opposite direction away from the RF transmitter orthe high RSSI area.

Moreover, by laying out waypoints at different distances and elevationsfrom RF transmitter tower 310, UAV 220 can generate a more complete RSSImap based on the RSSI readings at each waypoint (e.g., and locationsbetween waypoints). For example, while flying from waypoint to waypoint,UAV 310 can record RSSI mapping data, including current locationinformation and the RSSI information for signals received at the UAV'scurrent location. The current location information can include alocation determined based on satellite signals, Wi-Fi signals, cellularsignals, and/or other signals, according to well-known trilaterationtechniques. The current location information can include photogrammetricdata (e.g., photographs of ground control points, photographs of tower310, etc.). The RSSI information can include the frequency, amplitude,and/or RSSI value for the received signal. UAV 220 can store the RSSImapping data and generate the RSSI map. UAV 220 can send the RSSImapping data to flight planning system 102 so that flight planningsystem 102 (or a client device) can generate the RSSI map.

FIG. 6 is an illustration of a modified flight plan 600 generated basedon an aerial survey of the area around a target object. For example,while the initial flight plan 500 can be generated by flight planningsystem 102 based on a static target definition and/or map data, flightplan 600 can be generated by modifying flight plan 500 to account forthe actual RF signals generated by RF transmitter tower 310.

In some implementations, UAV 220 can determine the current RF signalconditions around RF transmitter tower 310 by performing a RSSI surveyof RF transmitter tower 310 and surrounding areas. For example, UAV 220can be configured to fly to a safe distance (e.g., ring 510) away fromRF transmitter tower 310. When UAV 220 reaches the safe distance, UAV220 can initiate an RSSI survey of RF transmitter tower 310 using a RSSIsensor (e.g., RF signal sensor 222, RF signal sensor 223) to generate aRSSI map of the area surrounding RF transmitter tower 310. For example,UAV 220 can gradually fly closer to RF transmitter tower 310 and collectRF mapping data (e.g., location information, RF signal information,photogrammetry data, etc.), as described above. UAV 220 can take anoptical survey of RF transmitter tower 310 using an optical sensor(e.g., optical imaging sensor 224, a camera, etc.) to generate imagesthat can be analyzed (e.g., by a computer, by a human) to inspect tower310 and RF transmitters attached to tower 310.

While conducting the RSSI survey, UAV 220 can dynamically adjust theUAV's flight plan and/or flight path to account for detected RF signalstrength detected around tower 310. For example, UAV 220 may detect RSSIvalues that indicate a signal distribution around tower 310 that differsfrom the expected signal distribution indicated in the default RSSI map,as indicated by the operator or manufacturer of RF transmitter tower 310and/or the operator or manufacturer of the transmitters attached to RFtransmitter 310. For example, UAV 220 can detect RSSI values thatindicate a signal strength at various locations that is stronger orweaker than the expected values. UAV 220 can detect RSSI values thatindicate the transmitter is broadcasting in a different direction ororientation than expected. UAV 220 can detect RSSI values that indicatethe RF transmitter is generating a different number of lobes thanexpected. For example, UAV 220 can detect that an RF transmitter ontower 310 is generating more lobes than the three (e.g., main lobe andtwo side lobes) originally expected.

In response to detecting these variations from the expected RSSIdistributions (e.g., as indicated by manufacturer or operator data), UAV220 can adjust the flight plan and/or flight path of UAV 220. Forexample, UAV 220 can dynamically adjust its flight plan to add geofences602 and/or 604 to account for the additional two lobes detected duringthe RSSI survey. UAV 220 can dynamically adjust (e.g., expand or shrink)geofences 506, 507, and 508 according to the differences between theexpected RSSI values and the actual RSSI measurements. UAV 220 candynamically adjust (e.g., change orientation) geofences 506, 507, 508 toaccount for the actual orientation of the corresponding lobes, asdetermined by the actual RSSI measurements. As described above, theboundaries of the geofences can be generated or modified based on the RFsignal strength limits (e.g., safe operating threshold) of UAV 220. UAV220 can use the actual RSSI measurements and/or geofences to avoid areasaround tower 310 where the signal strength of transmitted signals mightinterfere with the operation of UAV 220. For example, UAV 220 can removeor exclude from its flight path waypoints (e.g., waypoint 534) in theinitial flight plan that coincide with geofences 506, 507, 508, 602and/or 604.

In some implementations, UAV 220 can dynamically adjust its flight basedon real-time RSSI measurements. For example, UAV 220 can monitor RSSImeasurements as UAV 220 flies along a flight path from waypoint towaypoint. UAV 220 can detect increasing RSSI values and automaticallyadjust its flight path when UAV 220 reaches a location where the RSSImeasurements exceed a safe operating threshold value, as describedabove. For example, UAV 220 can change directions (e.g., up, down, left,right, forward, backward, etc.) to move away from or skirt an areahaving high RSSI values that are greater than the safe RSSI thresholdvalue specified for UAV 220.

In some implementations, UAV 220 can use the actual RSSI measurements togenerate an RSSI map (e.g., volumetric, three dimensional map) of thearea surrounding tower 310 that describes the frequencies, amplitudes,and/or signal strengths of signals received at various locations aroundtower 310. UAV 220 can send the RSSI measurements and/or RSSI map to GCS150 and/or flight planning system 102 for additional processing. Forexample, UAV 220, GCS 150, and/or flight planning system 102 can analyzethe RSSI measurements and/or RSSI map to determine the shape of RFsignal lobes generated by RF transmitters.

UAV 220, GCS 150, and/or flight planning system 102 can analyze the RSSImeasurements and/or RSSI map to determine whether the RF transmittersare aimed in the appropriate direction or azimuth (e.g., as specified bythe RF transmitter operator). For example, UAV 220, GCS 150, and/orflight planning system 102 can analyze the RSSI measurements and/or RSSImap to determine the orientation, shape, and/or direction of RF signalbeams originating from an RF transmitter on tower 310. UAV 220, GCS 150,and/or flight planning system 102 can analyze the RSSI measurementsand/or RSSI map to use the RF signal beam information to determine thelocation and/or orientation of the RF transmitter on tower 310. UAV 220,GCS 150, and/or flight planning system 102 can analyze the RSSImeasurements and/or RSSI map to determine whether the RF transmitters ontower 310 are operating properly (e.g., broadcasting at the desiredfrequency and/or power). If UAV 220, GCS 150, and/or flight planningsystem 102 determines that the RF transmitters are not configuredcorrectly, GCS 150 and/or flight planning system 102 can notify the UAVoperator, and/or RF transmitter operator that the RF transmitter is notoperating as desired or specified.

FIG. 7 illustrates an example flight path 700 for inspecting thealignment of RF transmitters. For example, some RF transmitter towersare configured with RF transmitters that communicate directly with enduser devices. For example, cellular data RF transmitters use radioaccess technology to allow smartphone users access to a cellular datanetwork. However, some tower mounted RF transmitters (e.g.,transceivers) communicate with RF receivers (e.g., transceivers) mountedon other towers to enable an RF data network. For example,communications towers can be configured with microwave transceivers thattransmit high power RF signals to other communications towers toestablish a RF data network between towers. This tower to towercommunication mechanism works best (e.g., most efficiently) when the RFsignal beams are properly aligned between RF transmitter and RFreceiver. Thus, in some implementations, UAV 220 can fly an aerialinspection mission to inspect the alignment of the RF transmitter and RFreceiver.

In some implementations, mission planning module 210 can generate flightplan for performing an RF transmitter alignment inspection mission. Forexample, flight planning system 102 can receive mission request 202indicating that the UAV operator would like to fly an RF transmitteralignment inspection mission. Mission request 202 can, for example,identify both RF transmitter tower 310 and RF transmitter tower 710 astargets of the alignment inspection mission. When mission planningmodule 210 receives the alignment inspection mission request, missionplanning module 210 can use the location and height information for eachtower 310 and 710 to determine a likely signal path 720 between towers310 and 710. Mission planning module 210 can then generate a flight pathfor intercepting an RF signal beam sent from RF transmitter tower 310 toRF receiver tower 710. In some implementations, the same flight path canbe used to intercept an RF signal beam send from RF transmitter tower710 to RF receiver tower 310.

In some implementations, mission planning module 210 can generate aflight plan that includes reserved airspace geofence 702. For example,mission planning module 210 can reserve the airspace needed for thealignment inspection mission at a location between tower 310 and tower710. Mission planning module 210 can select the airspace to reservebased on signal path 720, obstructions near signal path 720, and/orno-fly zones along signal path 720. For example, mission planning module210 can select airspace such that signal path 720 is centered (or nearlycentered) in the reserved airspace and is not over a populated area(e.g., no-fly zone). After selecting the airspace, mission planningmodule 210 can generate geofence 702 to define the boundaries of thethree-dimensional reserved airspace.

In some implementations, mission planning module 210 can generate aflight path for intercepting a signal beam travelling between towers 310and 710. For example, mission planning module 210 can generate a flightpath resembling concentric circles centered on and/or orientedperpendicularly (or nearly perpendicularly) to the expected signal path720 between towers 310 and 710, as illustrated by FIG. 7. The waypoints(e.g., represented by triangles) along the flight path can be orderedsuch that UAV 220 flies from the largest, outermost circle inwardstoward the smallest circle at the center of the concentric circles. Forexample, UAV 220 can fly to each waypoint (e.g., waypoint 704) in theoutermost circle before transitioning inward to the next circle. UAV 220can fly to each waypoint (e.g., waypoint 706) in the current circlebefore transitioning inward to fly to the waypoints (e.g., waypoint 708)the next circle until UAV 220 reaches the center of the circles. Thecircular flight path described above is one example of a flight paththat may be generated by mission planning module 210. Other flight pathsthat may be generated by mission planning module 210 may resemble arectangular grid or three dimensional shapes like a sphere or cube.

While flying along the flight path, UAV 220 can collect RF signalinformation (e.g., RSSI, frequency, amplitude, etc.) for the signalsreceived from tower and location information (e.g., photogrammetry data,satellite signal data, latitude, longitude, altitude, etc.) describingthe position of UAV 220 when the signals were received. For example, UAV220 can include a single RF signal sensor 222 (e.g., a directionalantenna and RF receiver) for receiving signals coming from the directionof tower 310. For example, UAV 220 can fly with signal sensor 222directed at tower 310 to receive RF signals generated by tower 310. Whensignals are received from tower 310, UAV 220 can record the RSSI,frequency and/or amplitude for the received signal along with thelocation information describing the current location of UAV 220 when thesignals were received.

Based on the RF signal information and location information, UAV 220 candetermine an RSSI map for the received signal from which UAV 220 candetermine the origination (e.g., transmitter location) and orientationof the received signal. Based on the signal origination and orientation,UAV 220 can determine whether the transmitter sending the RF signal isconfigured correctly to transmit a signal to tower 710. UAV 220 can flya similar mission to determine whether signals transmitted fromtransmitters on tower 710 are configured correctly (e.g., aimedcorrectly) for transmitting signals from tower 710 to tower 310.

In some implementations, UAV 220 can be configured to collect RF signalinformation from tower 310 and tower 710 simultaneously. For example,UAV 220 can be configured with two RF signal sensors for collecting RFsignal information from transmitters on tower 310 and tower 710 at aboutthe same time. UAV 220 can include directional RF sensor 222 anddirectional RF sensor 223, for example. RF sensor 222 and RF sensor 223can be oriented 180 degrees apart (e.g., in opposite directions) so thatUAV 220 can receive or detect signals from transmitters on both tower310 and tower 710 at the same time.

As described above, when UAV 220 receives the signals from tower 310and/or tower 710, UAV 220 can determine the RSSI, frequency, and/orwavelength of the signal and store the signal information along withlocation information describing the location of UAV 220 when the signalwas received. Based on the RF signal information and locationinformation, UAV 220 can determine an RSSI map (or multiple RSSI maps)for the signals received from both tower 310 and tower 710. UAV 220 canuse the RSSI maps to determine the origination (e.g., transmitterlocation) and orientation of the signals received from towers 310 and710. Based on the signal origination and orientation, UAV 220 candetermine whether the transmitters sending the RF signals from towers310 and 710 are configured (e.g., oriented) correctly to transmit asignal to tower 710 and 310, respectively. Thus, UAV 220 can collect thesignal information necessary to inspect the alignment oftransmitters/receivers on both tower 310 and tower 710 simultaneously.

Example Processes

FIG. 8 is a flow diagram of an example process 800 for generating aflight plan for inspecting an RF transmitter tower. For example, process800 can be performed by flight planning system 102 to prepare orconfigure UAV 220 to perform a RF transmitter tower inspection missionwhile avoiding areas where RF signal strength may cause damage to UAV220, as described above. Process 800 can be performed by flight planningsystem 102 of FIG. 1 in response to receiving a RF transmitter towerinspection mission request from a UAV operator.

At step 802, flight planning system 102 can receive RF transmitter towerinspection mission parameters. For example, flight planning system 102can receive the mission parameters in mission request 202 of FIG. 2.

At step 804, flight planning system 102 can model the inspection targetobject. For example, flight planning system 102 can model the RFtransmitter tower based on a target definition received in missionrequest 202. For example, flight planning system 102 can generate adigital three-dimensional model of the RF transmitter tower and thesurrounding airspace.

At step 806, flight planning system 102 can determine points of intereston the inspection target. For example, flight planning system 102 candetermine points of interest for inspecting on the RF transmitter towerbased on inspection points or inspection areas defined in missionrequest 202, as described above.

At step 808, flight planning system 102 can determine default RFconditions around the inspection target object. For example, flightplanning system 102 can obtain information describing the default orexpected transmission frequencies and transmission power of RFtransmitters on of the RF transmitter tower to be inspected. Forexample, flight planning system 102 can obtain RSSI maps for the variousfrequencies transmitted by RF transmitters mounted on the RF transmittertower that shows the expected RSSI values for the various frequencies atdifferent locations within the volumetric areas or airspace around theRF transmitter tower.

At step 810, flight planning system 102 can determine restrictedairspace based on the default RF conditions around the RF transmittertower. For example, flight planning system 102 can determine locationsand/or areas around the RF transmitter tower where the RSSI values aregreater than a maximum safe RSSI threshold value specified for UAV 220.Flight planning system 102 can identify airspace where the expected RSSIvalues exceed the minimum safe RSSI threshold value for UAV 220 asrestricted airspace.

At step 812, flight planning system 102 can generate a flight plan basedon the target object model, the points of interest, and the default RFconditions. For example, flight planning system 102 can determine no-flyzones (e.g., geofences) based on the restricted airspaces determined atstep 810. Flight planning system 102 can select way points for theflight plan based on the object model and points of interest that allowsthe UAV to inspect the points of interest without flying into the no-flyzones around the target object. Flight planning system 102 can definecontingency events and corresponding contingency maneuvers for theflight plan based on the no-fly zones, UAV operating thresholds (e.g.,RSSI thresholds), and/or other conditions, as described above.

At step 814, flight planning system 102 can generate a flight packagethat includes the flight plan. For example, flight planning system 102can generate a flight package that provides configuration data and/orprogramming for the UAV to fly (e.g., autopilot) the RF transmittertower inspection mission.

At step 816, flight planning system 102 can send the flight package tothe UAV. For example, flight planning system 102 can send the flightpackage to UAV 220 to configure UAV 220 to fly the RF transmitter towerinspection mission defined in the flight package.

FIG. 9 is a flow diagram of an example process 900 for executing aflight plan for inspecting an RF transmitter tower. For example, process900 can be performed by UAV 220 based on a flight package generated byflight planning system 102, as described above.

At step 902, UAV 220 can receive a flight package. For example, UAV 220can receive the flight package generated by flight planning system 102for inspecting a RF transmitter tower, as described above. The flightpackage can include a model of the RF transmitter tower to be inspected,locations of inspection points on the RF transmitter tower, a flightplan including way points for inspecting the RF transmitter tower,standoff distances calculated for capturing images having a specifiedsurface sampling distance, geofences defining reserved airspace and/orno-fly zones, contingency events and corresponding contingencymaneuvers, and/or other information necessary for performing an aerialinspection of the targeted RF transmitter tower or towers.

At step 904, UAV 220 can conduct an initial survey of the inspectiontarget object. For example, before executing the flight plan or at thebeginning of the flight plan, UAV 220 can fly to a safe distance awayfrom the RF transmitter tower and perform a RSSI survey of the areaaround the RF transmitter tower using RF signal sensors configured onUAV 220. For example, UAV 220 can perform an initial survey focused onspecific frequencies specified in the flight package. UAV 220 canperform an initial survey of all frequencies when no specificfrequencies are specified in the flight package.

At step 906, UAV 220 can generate a map of the current RF conditionsaround the inspection target. For example, based on the initial survey,UAV 220 can generate one or more RSSI maps that describe the RSSI valuesdetected for various RF frequencies at various locations around the RFtransmitter tower.

At step 908, UAV 220 can adjust the flight plan based on the generatedRSSI map. For example, UAV 220 can adjust the flight plan based on thecurrent RF conditions around the RF transmitter tower. UAV 220 canadjust the flight plan by generating no-fly zones/geofences aroundvolumetric areas (e.g., airspaces) having high RSSI values that maydamage UAV 220 and/or interfere with the operation of UAV 220. UAV 220can remove way points that correspond to locations within the no flyzones from the flight plan. UAV 220 may change the order or sequence ofthe way points in the flight plan and/or make other modifications to theflight plan, as described herein above.

At step 910, UAV 220 can conduct the inspection mission based on theadjusted flight plan. For example, UAV 220 can fly to the way pointsspecified in the adjusted flight plan and capture optical images ofpoints of interest on the RF transmitter tower. UAV 220 can fly to theway points specified in the adjusted flight plan and capture RF signalmapping data at various locations around the RF transmitter tower. Forexample, the RF signal mapping data can include RF signal informationdescribing the frequency, wavelength, and/or RSSI value of a detected RFsignal. The RF signal mapping data can include location information thatincludes photogrammetric images and/or location data (e.g., geographiccoordinates and altitude) derived from satellite, cellular, and/or Wi-Fisignals. The RF signal mapping data can associate the RF signalinformation with the corresponding location information describing wherethe RF signal information was detected so that a RF signal map can begenerated that represents the detected signals at correspondinglocations around the RF transmitter tower.

At step 912, UAV 220 can detect the occurrence of a contingency event.For example, UAV 220 can detect a contingency event when UAV 220receives a signal having an RSSI value that exceeds the maximum safeRSSI threshold value for UAV 220. UAV can detect a contingency eventwhen UAV 220 enters a restricted airspace (e.g., no-fly zone) geofence.UAV 220 can detect a contingency event when UAV 220 moves closer than athreshold distance from the RF transmitter tower. UAV 220 can detectother contingency events, as may described herein.

At step 914, UAV 220 can perform a contingency maneuver. For example,UAV 220 can perform a contingency maneuver in response to detecting acontingency event. For example, UAV 220 can perform a contingencymaneuver that causes UAV 220 to fly to the previous way point in theflight plan. UAV 220 can perform a contingency maneuver that causes UAV220 to fly to an emergency landing location and land. UAV 220 canperform a contingency maneuver that causes UAV 220 to reverse courseand/or fly a distance away from the RF transmitter tower avoid airspacewhere UAV 220 has detected RSSI values that exceed the safe RSSIthreshold value for UAV 220. UAV 220 can perform a contingency maneuverthat causes UAV 220 to exit a restricted airspace geofence. UAV 220 canperform a contingency maneuver that causes UAV 220 to skip the RFtransmitter tower inspection at the current way point that has an RSSIvalue that exceeds a maximum safe RSSI threshold value, fly to the nextway point in the flight plan that has an RSSI value that is less thanthe maximum safe RSSI threshold value for UAV 220, and continue theflight plan.

Many of the implementations described include UAV 220 performing datacollection using various sensors and data analysis to determine safe orunsafe airspace, generate geofences, generate RF signal maps, etc.However, according to some implementations, UAV 220 can send sensor data(e.g., imaging sensor data, RF signal sensor data, etc.) to flightplanning system 102 and/or GCS 150 for analysis. Thus, in someimplementations, flight planning system 102 and/or GCS 150 may performthe sensor data analysis to determine safe or unsafe airspace, generategeofences, and/or generate RF signal maps. After performing the analysisof the sensor data and determining safe or unsafe airspace, generatinggeofences, and/or generating RF signal maps, flight planning system 102and/or GCS 150 can send an updated or modified flight plan to UAV 220that includes the updated flight plan, geofences, RF signal maps, etc.,so that UAV 220 can continue flying the RF transmitter tower inspectionmission in a safe manner.

In some implementations, when UAV 220, flight planning system 102,and/or GCS 150 generates an RF signal map (e.g., RSSI map, signaldistribution map, etc.), flight planning system 102, and/or GCS 150 cansend the RF signal map to the UAV operator that requested the RFtransmitter tower mission sot that the UAV operator and/or RFtransmitter tower operator can determine whether the RF transmittertower is operating as desired.

Example System Architecture

FIG. 10 illustrates a block diagram of an example system architecture1000 for an unmanned aerial vehicle (UAV). For example, systemarchitecture 1000 can be configured with the hardware and/or softwarefor implementing the UAV features and processes described herein. Systemarchitecture 1000 can correspond to UAV 160, as described above withreference to FIG. 1.

In some implementations, system architecture 1000 can include primaryprocessing system 1002. For example, primary processing system 1002 canbe a system of one or more computers, including hardware and/orsoftware, that is in communication with, or maintains, one or moredatabases. In some implementations, primary processing system 1002 caninclude one or more processors 1004 (e.g., CPU, application processor,etc.), graphics processors 1006 (e.g., GPU), and/or I/O subsystem 1008.In some implementations, primary processing system 1002 can includeadditional or different logic circuits, analog circuits, associatedvolatile and/or non-volatile memory, associated input/output data ports,power ports, etc., not shown. Similarly, primary processing system caninclude various software processes executing on processors 1004 or othercomputers included in primary processing system 1002.

In some implementations, memory 1020 may include non-volatile memory,such as one or more magnetic disk storage devices, solid state harddrives, or flash memory. Other volatile memory such a RAM, DRAM, SRAMmay be used for temporary storage of data while the UAV is operational.Memory 1020 may include databases for storing information describing UAVflight operations, flight plans, contingency events, geofenceinformation, component information, and other information. Memory 1020may include various modules, programs, applications, and/or instructionsthat cause the UAV to perform flight operations, contingency maneuvers,missions, and other functions.

In some implementations, memory 1020 can include operating system 1022.For example, operating system 1022 can be a real time operating system(RTOS), UNIX, LINUX, OS X, WINDOWS, ANDROID or other operating system.Operating system 1022 may include instructions for handling basic systemservices and for performing hardware dependent tasks. However, othersoftware modules and/or applications may be executed as operating systemprocesses. For example, flight control module 1024, contingency module1026, and/or mission module 1028, may be part of operating system 1020and may be executed as operating system processes.

In some implementations, memory 1020 can include flight control module1024. For example, flight control module 1024 (e.g., flight controlmodule 164) can be configured to handle flight control operations forthe UAV. Flight control module 1024 can interact with one or morecontrollers 1040 that control operation of motors 1042 and/or actuators1044. For example, motors 1042 may be used for rotation of UAVpropellers. Actuators 1044 may be used for UAV flight surface controlsuch as ailerons, rudders, flaps, landing gear, and parachutedeployment.

In some implementations, memory 1020 can include contingency module1026. For example, contingency module 1026 (e.g., contingency module166) can monitor and handle UAV contingency events. For example,contingency module 1026 may detect that the UAV has crossed a border ofa geofence, and then instruct flight control module 1024 to return to apredetermined landing location. Contingency module 1026 can detect othercontingency events, including a low battery or fuel state, a malfunctionof an onboard sensor, motor, or other component, and/or a deviation fromthe flight plan. When contingency module 1026 detects a contingencyevent, contingency module 1026 can instruct flight control module 1024to return to a predetermined landing location or perform some othercontingency operation. For example, if the UAV is equipped with aparachute, contingency module 1026 may cause the deployment of theparachute when a motors and/or actuator fails. The foregoing is notmeant to be limiting, as contingency module 1026 may detect othercontingency events and/or perform other contingency operations.

In some implementations, memory 1020 can include mission module 1028.For example, mission module 1028 (e.g., mission module 162) can processflight plans, waypoints, and other associated information with a flightplan as provided to the UAV in a flight package. For example, a flightpackage can include one or more flight plans. Each flight plan canincluding a flight schedule (e.g., start time, end time), startlocation, destination location, waypoints for navigating from the startlocation to the destination location, contingency event definitions,contingency operations for each contingency event. The flight packagecan include operator (e.g., pilot) information, such as the name of theoperator, the operator's employer, the operator's license information(e.g., including UAV ratings), etc. The flight package can include UAVinformation, such as the UAV type, payload, model, size, operatingrange, an/or other UAV specifications describing the UAV that willperform the mission described by the flight package. In someimplementations, mission module 1028 can work in conjunction with flightcontrol module 1024. For example, mission module 1028 can sendinformation concerning the flight plan to flight control module 1024.For example, mission module 1028 can send flight control module 1024 theflight start location, end location, waypoint coordinates (e.g.,latitude, longitude), flight altitude, flight velocity, etc., so thatthe flight control module 1024 can automatically pilot the UAV along theflight path.

Various sensors, devices, firmware and other systems may beinterconnected to support multiple functions and operations of the UAV.For example, the UAV primary processing system 1002 may use varioussensors to determine the vehicle's current geo-spatial location,attitude, altitude, velocity, direction, pitch, roll, yaw and/orairspeed and to pilot the vehicle along a specified route and/or to aspecified location and/or to control the vehicle's attitude, velocity,altitude, and/or airspeed (optionally even when not navigating thevehicle along a specific path or to a specific location).

In some implementations, primary processing system 1002 may be coupledto one or more sensors 1050, such as magnetometer 1052, pressure sensors(static or differential) 1054, temperature sensors 1056, gyroscopes1058, accelerometers 1060, and/or other sensors 1062, such as currentsensors, voltage sensors, hydrometer, motor sensors and/or any othersensors, as may be described herein.

In some implementations, primary processing system 1002 may use aninertial measurement unit (IMU) 1010 for use in navigating the UAV. Forexample, IMU 1010 can use measurements from magnetometer 1052, gyroscope1058, accelerometer 1060 and/or other sensors to determine the specificforce of the UAV, the angular rate of the UAV, and/or magnetic fieldsurrounding the UAV. Sensors 1050 and/or other components ofarchitecture 1000 can be coupled to primary processing system 1002, orto controller boards coupled to primary processing system 1002, usingone or more communication buses, such as a controller area network(e.g., CAN) bus, or other signal lines.

In some implementations, primary processing system 1002 may have variousdevices 1060 connected to it for data collection. For example, devices1060 can include one or more cameras 1062. For example, cameras 1062 caninclude digital (e.g., CMOS image sensor) or analog (e.g. film)photographic imaging devices. Cameras 1062 can include, for example, avideo cameras, an infra-red camera, and/or a multispectral camera.Devices 1060 can include payload device 1064. For example, payloaddevice 1064 can be a mission-specific device used by primary processingsystem 1002 to collect mission-specific data and information forperforming mission-specific tasks, such as collecting data needed toperform the processes and functions described above with reference toFIGS. 1-9.

In some implementations, devices 1060 can include additional sensors orelectronic systems, such as Lidar, radio transceivers, sonar, and/or atraffic collision avoidance system (TCAS), video camera, infra-redcamera, multispectral camera, stereo camera pair, Lidar, radiotransceiver, sonar, laser ranger, altimeter, ADS-B (Automatic dependentsurveillance—broadcast) transponder, etc.

In some implementations, primary processing system 1002 can interactwith devices 1060 through controllers 1066. For example, controllers1066 may be used to interact with and/or operate camera 1062 and/orpayload device 1064. Data collected by devices 1060 may be stored on thedevice collecting the data (e.g., in camera 1062, in payload device1064, etc.), or the data may be stored on non-volatile memory 1020 ofprimary processing system 1002.

In some implementations, primary processing system 1002 may be coupledto communication subsystem 1070. For example, communication subsystem1070 can include a global navigational satellite system (GNSS, GPS,etc.) receiver 1072 for receiving satellite signals used by primaryprocessing system 1002 to determine the current location of the UAV.

In some implementations, communication subsystem 1070 can include radiotransceiver 1074. For example, a UAV ground station (e.g., stationary ormobile) can send command and control signals to the UAV using radiotransmissions to manually control the UAV. The UAV can receive thecommand and control signals using radio transceiver 1074. In someimplementations, radio transceiver 1074 can be used for wireless orwired data transmission to and from the UAV primary processing system1002, and optionally the UAV secondary processing system 1002.

In some implementations, the UAV may use one or more communicationssubsystems 1070, such as a wireless communication or wired subsystem, tofacilitate communication to and from the UAV. Wireless communicationsubsystems 1070 may include radio transceivers, and infrared, opticalultrasonic, electromagnetic devices. Wired communication systems 1070may include ports such as Ethernet, USB ports, serial ports, or othertypes of port to establish a wired connection to the UAV with otherdevices, such as a ground control system, flight planning system, orother devices, for example a mobile phone, tablet, personal computer,display monitor, other other network-enabled devices. The UAV may use alight-weight tethered wire to a ground control station for communicationwith the UAV. The tethered wire may be removeably affixed to the UAV,for example via a magnetic coupler.

In some implementations, flight data logs may be generated by obtainingvarious information from the UAV sensors 1050, devices 1060,communication subsystems 1070, operating system 1022 and/or othercomponents of UAV system architecture 1000 and storing the informationin non-volatile memory. The data logs may include a combination ofvarious data, such as time, altitude, heading, ambient temperature,processor temperatures, pressure, battery level, fuel level, absolute orrelative position, GPS coordinates, pitch, roll, yaw, ground speed,humidity level, velocity, acceleration, contingency information. Thisforegoing is not meant to be limiting, and other data may be capturedand stored in the flight data logs. The flight data logs may be storedon a removable media and the media installed onto the ground controlsystem. Alternatively, the data logs may be wirelessly transmitted tothe ground control system or to the flight planning system.

In addition to the UAV primary processing system 1002, a secondaryprocessing system 1082 may be used to run a secondary computingenvironment 1080 within the UAV for performing other processes orfunctions, such as the process and functions for dynamically adjustingUAV flight operations based on thermal sensor data, as described abovewith reference to FIGS. 1-9. For example, typically flight criticalfunctions of the UAV will be performed using primary processing system1002, while mission specific, secondary, or auxiliary functions of theUAV may be performed using secondary processing system 1082. Further,even though secondary processing system 1082 operates in secondarycomputing environment 1080, secondary processing system 1082 may be ableto access memory 1020, sensors 1050, devices 1060, and/or communicationsubsystem 1070 (e.g., through primary processing system 1002) in orderto perform various processes and/or functions, such as the process andfunctions for dynamically adjusting UAV flight operations based onthermal sensor data, as described above with reference to FIGS. 1-9.

In some implementations, UAV secondary processing system 1082 can be asystem of one or more computers, or software executing on a system ofone or more computers, which is in communication with, or maintains, oneor more databases. The UAV secondary processing system 1082 can includeone or more processors 1084, graphics processors 1086, and/or I/Osubsystem 1088. In some implementations, secondary processing system1082 can include other or additional components, such as logic circuits,analog circuits, associated volatile and/or non-volatile memory,associated input/output data ports, power ports, etc. Secondaryprocessing system 1082 can include one or more software processes,modules, instructions executing on processors 1084, GPU 1086, and/orother components of secondary processing system 1082.

In some implementations, secondary processing system 1082 can be coupledto memory 1090 in secondary computing environment 1080. For example,memory 1090 may include non-volatile memory, such as one or moremagnetic disk storage devices, solid state hard drives, flash memory.Memory 1090 may include volatile memory such a RAM, DRAM, SRAM that maybe used for storage of data, applications, instructions, etc., while theUAV is operational. Ideally modules, applications and other functionsrunning on the secondary processing system 1082 will be non-criticalfunctions in nature, that is, if the function fails, the UAV will stillbe able to safely operate.

In some implementations, memory 1090 can include operating system 1092.For example, operating system 1092 can be a real time operating system(RTOS), UNIX, LINUX, OS X, WINDOWS, ANDROID or other operating system.Operating system 1092 may include instructions for handling basic systemservices and for performing hardware dependent tasks. However, in someimplementations, operating system 1092 may include instructions forhandling the processes and functions as described above with referenceto FIGS. 1-9.

In some implementations, memory 1090 can include other software modules1094. For example, other software modules 1094 and/or applications maybe run by secondary processing system 1082 in secondary computingenvironment 1080, such as software modules and/or application forperforming the processes and functions described above with reference toFIGS. 1-9.

FIG. 13A and FIG. 13B show example system architectures 1300 and 1350for the computing devices performing the various operations, processes,and functions described herein. The more appropriate embodiment will beapparent to those of ordinary skill in the art when practicing thepresent technology. For example, system architectures 1300 and/or 1350can correspond to flight planning system 102, user device 140, and/orground control system 150, described above with reference to FIG. 1.System architectures 1300 and/or 1350 may be incorporated into systemarchitecture 1000 to enable the various operations, processes, functionsand features of UAV 160. Persons of ordinary skill in the art will alsoreadily appreciate that other system embodiments are possible.

FIG. 13A illustrates a conventional system bus computing systemarchitecture 1300 wherein the components of the system are in electricalcommunication with each other using a bus 1305. Example system 1300includes a processing unit (CPU or processor) 1310 and a system bus 1305that couples various system components including the system memory 1315,such as read only memory (ROM) 1320 and random access memory (RAM) 1325,to the processor 1310. The system 1300 can include a cache of high-speedmemory connected directly with, in close proximity to, or integrated aspart of the processor 1310. The system 1300 can copy data from thememory 1315 and/or the storage device 1330 to the cache 1312 for quickaccess by the processor 1310. In this way, the cache can provide aperformance boost that avoids processor 1310 delays while waiting fordata. These and other modules can control or be configured to controlthe processor 1310 to perform various actions. Other system memory 1315may be available for use as well. The memory 1315 can include multipledifferent types of memory with different performance characteristics.The processor 1310 can include any general purpose processor and ahardware module or software module, such as module 1 1332, module 21334, and module 3 1336 stored in storage device 1330, configured tocontrol the processor 1310 as well as a special-purpose processor wheresoftware instructions are incorporated into the actual processor design.The processor 1310 may essentially be a completely self-containedcomputing system, containing multiple cores or processors, a bus, memorycontroller, cache, etc. A multi-core processor may be symmetric orasymmetric.

To enable user interaction with the computing device 1300, an inputdevice 1345 can represent any number of input mechanisms, such as amicrophone for speech, a touch-sensitive screen for gesture or graphicalinput, keyboard, mouse, motion input, speech and so forth. An outputdevice 1335 can also be one or more of a number of output mechanismsknown to those of skill in the art. In some instances, multimodalsystems can enable a user to provide multiple types of input tocommunicate with the computing device 1300. The communications interface1340 can generally govern and manage the user input and system output.There is no restriction on operating on any particular hardwarearrangement and therefore the basic features here may easily besubstituted for improved hardware or firmware arrangements as they aredeveloped.

Storage device 1330 is a non-volatile memory and can be a hard disk orother types of computer readable media which can store data that areaccessible by a computer, such as magnetic cassettes, flash memorycards, solid state memory devices, digital versatile disks, cartridges,random access memories (RAMs) 1325, read only memory (ROM) 1320, andhybrids thereof.

The storage device 1330 can include software modules 1332, 1334, 1336for controlling the processor 1310. Other hardware or software modulesare contemplated. The storage device 1330 can be connected to the systembus 1305. In one aspect, a hardware module that performs a particularfunction can include the software component stored in acomputer-readable medium in connection with the necessary hardwarecomponents, such as the processor 1310, bus 1305, display 1335, and soforth, to carry out the function.

FIG. 13B illustrates a computer system 1350 having a chipsetarchitecture that can be used in executing the described method andgenerating and displaying a graphical user interface (GUI). Computersystem 1350 is an example of computer hardware, software, and firmwarethat can be used to implement the disclosed technology. System 1350 caninclude a processor 1310, representative of any number of physicallyand/or logically distinct resources capable of executing software,firmware, and hardware configured to perform identified computations.Processor 1310 can communicate with a chipset 1360 that can controlinput to and output from processor 1310. In this example, chipset 1360outputs information to output 1365, such as a display, and can read andwrite information to storage device 1370, which can include magneticmedia, and solid state media, for example. Chipset 1360 can also readdata from and write data to RAM 1375. A bridge 1380 for interfacing witha variety of user interface components 1385 can be provided forinterfacing with chipset 1360. Such user interface components 1385 caninclude a keyboard, a microphone, touch detection and processingcircuitry, a pointing device, such as a mouse, and so on. In general,inputs to system 1350 can come from any of a variety of sources, machinegenerated and/or human generated.

Chipset 1360 can also interface with one or more communicationinterfaces 1390 that can have different physical interfaces. Suchcommunication interfaces can include interfaces for wired and wirelesslocal area networks, for broadband wireless networks, as well aspersonal area networks. Some applications of the methods for generating,displaying, and using the GUI disclosed herein can include receivingordered datasets over the physical interface or be generated by themachine itself by processor 1310 analyzing data stored in storage 1370or 1375. Further, the machine can receive inputs from a user via userinterface components 1385 and execute appropriate functions, such asbrowsing functions by interpreting these inputs using processor 1310.

It can be appreciated that example systems 1300 and 1350 can have morethan one processor 1310 or be part of a group or cluster of computingdevices networked together to provide greater processing capability.

For clarity of explanation, in some instances the present technology maybe presented as including individual functional blocks includingfunctional blocks comprising devices, device components, steps orroutines in a method embodied in software, or combinations of hardwareand software.

Any of the steps, operations, functions, or processes described hereinmay be performed or implemented by a combination of hardware andsoftware modules, alone or in combination with other devices. In anembodiment, a software module can be software that resides in memory ofa client device and/or one or more servers of a content managementsystem and perform one or more functions when a processor executes thesoftware associated with the module. The memory can be a non-transitorycomputer-readable medium.

In some embodiments the computer-readable storage devices, mediums, andmemories can include a cable or wireless signal containing a bit streamand the like. However, when mentioned, non-transitory computer-readablestorage media expressly exclude media such as energy, carrier signals,electromagnetic waves, and signals per se.

Methods according to the above-described examples can be implementedusing computer-executable instructions that are stored or otherwiseavailable from computer readable media. Such instructions can comprise,for example, instructions and data which cause or otherwise configure ageneral purpose computer, special purpose computer, or special purposeprocessing device to perform a certain function or group of functions.Portions of computer resources used can be accessible over a network.The computer executable instructions may be, for example, binaries,intermediate format instructions such as assembly language, firmware, orsource code. Examples of computer-readable media that may be used tostore instructions, information used, and/or information created duringmethods according to described examples include magnetic or opticaldisks, flash memory, USB devices provided with non-volatile memory,networked storage devices, and so on.

Devices implementing methods according to these disclosures can comprisehardware, firmware and/or software, and can take any of a variety ofform factors. Typical examples of such form factors include laptops,smart phones, small form factor personal computers, personal digitalassistants, and so on. Functionality described herein also can beembodied in peripherals or add-in cards. Such functionality can also beimplemented on a circuit board among different chips or differentprocesses executing in a single device, by way of further example.

The instructions, media for conveying such instructions, computingresources for executing them, and other structures for supporting suchcomputing resources are means for providing the functions described inthese disclosures.

Although a variety of examples and other information was used to explainaspects within the scope of the appended claims, no limitation of theclaims should be implied based on particular features or arrangements insuch examples, as one of ordinary skill would be able to use theseexamples to derive a wide variety of implementations. Further andalthough some subject matter may have been described in languagespecific to examples of structural features and/or method steps, it isto be understood that the subject matter defined in the appended claimsis not necessarily limited to these described features or acts. Forexample, such functionality can be distributed differently or performedin components other than those identified herein. Rather, the describedfeatures and steps are disclosed as examples of components of systemsand methods within the scope of the appended claims.

Each of the processes, methods, and algorithms described in thepreceding sections may be embodied in, and fully or partially automatedby, code modules executed by one or more computer systems or computerprocessors comprising computer hardware. The code modules may be storedon any type of, one or more, non-transitory computer-readable media(e.g., a computer storage product) or computer storage devices, such ashard drives, solid state memory, optical disc, and/or the like. Thesystems and modules may also be transmitted as generated data signals(for example, as part of a carrier wave or other analog or digitalpropagated signal) on a variety of computer-readable transmissionmediums, including wireless-based and wired/cable-based mediums, and maytake a variety of forms (for example, as part of a single or multiplexedanalog signal, or as multiple discrete digital packets or frames). Theprocesses and algorithms may be implemented partially or wholly inapplication-specific circuitry. The results of the disclosed processesand process steps may be stored, persistently or otherwise, in any typeof non-transitory computer storage such as, for example, volatile ornon-volatile storage.

In general, the term “module”, as used herein, refers to logic embodiedin hardware or firmware, or to a collection of software instructions,possibly having entry and exit points, written in a programminglanguage, such as, for example, Java, Lua, C or C++. A software modulemay be compiled and linked into an executable program, installed in adynamic link library, or may be written in an interpreted programminglanguage such as, for example, BASIC, Perl, or Python. It will beappreciated that software modules may be callable from other modules orfrom themselves, and/or may be invoked in response to detected events orinterrupts. Software modules configured for execution on computingdevices may be provided on one or more computer readable media, such asa compact discs, digital video discs, flash drives, or any othertangible media. Such software code may be stored, partially or fully, ona memory device of the executing computing device, such as airspacereservation module 302, for execution by the computing device. Softwareinstructions may be embedded in firmware, such as an EPROM. It will befurther appreciated that hardware modules may be comprised of connectedlogic units, such as gates and flip-flops, and/or may be comprised ofprogrammable units, such as programmable gate arrays or processors. Themodules described herein are preferably implemented as software modules,but may be represented in hardware or firmware. Generally, the modulesdescribed herein refer to logical modules that may be combined withother modules or divided into sub-modules despite their physicalorganization or storage.

User interfaces described herein are optionally presented (and userinstructions may be received) via a user computing device using abrowser, other network resource viewer, a dedicated application, orotherwise. Various features described or illustrated as being present indifferent embodiments or user interfaces may be combined into the sameembodiment or user interface. Commands and information received from theuser may be stored and acted on by the various systems disclosed hereinusing the processes disclosed herein. While the disclosure may referenceto a user hovering over, pointing at, or clicking on a particular item,other techniques may be used to detect an item of user interest. Forexample, the user may touch the item via a touch screen, or otherwiseindicate an interest. The user interfaces described herein may bepresented on a user terminal, such as a laptop computer, desktopcomputer, tablet computer, smart-phone, virtual reality headset,augmented reality headset, or other terminal type. The user terminalsmay be associated with user input devices, such as touch screens,microphones, touch pads, keyboards, mice, styluses, cameras, etc. Whilethe foregoing discussion and figures may illustrate various types ofmenus, other types of menus may be used. For example, menus may beprovided via a drop down menu, a toolbar, a pop up menu, interactivevoice response system, or otherwise.

The various features and processes described above may be usedindependently of one another, or may be combined in various ways. Allpossible combinations and subcombinations are intended to fall withinthe scope of this disclosure. In addition, certain method or processblocks may be omitted in some implementations. The methods and processesdescribed herein are also not limited to any particular sequence, andthe blocks or states relating thereto can be performed in othersequences that are appropriate. For example, described blocks or statesmay be performed in an order other than that specifically disclosed, ormultiple blocks or states may be combined in a single block or state.The example blocks or states may be performed in serial, in parallel, orin some other manner. Blocks or states may be added to or removed fromthe disclosed example embodiments. The example systems and componentsdescribed herein may be configured differently than described. Forexample, elements may be added to, removed from, or rearranged comparedto the disclosed example embodiments.

Conditional language used herein, such as, among others, “can,” “could,”“might,” “may,” “for example,” and the like, unless specifically statedotherwise, or otherwise understood within the context as used, isgenerally intended to convey that certain embodiments include, whileother embodiments do not include, certain features, elements and/orsteps. Thus, such conditional language is not generally intended toimply that features, elements and/or steps are in any way required forone or more embodiments or that one or more embodiments necessarilyinclude logic for deciding, with or without author input or prompting,whether these features, elements and/or steps are included or are to beperformed in any particular embodiment. The terms “comprising,”“including,” “having,” and the like are synonymous and are usedinclusively, in an open-ended fashion, and do not exclude additionalelements, features, acts, operations, and so forth. Also, the term “or”is used in its inclusive sense (and not in its exclusive sense) so thatwhen used, for example, to connect a list of elements, the term “or”means one, some, or all of the elements in the list. Conjunctivelanguage such as the phrase “at least one of X, Y and Z,” unlessspecifically stated otherwise, is otherwise understood with the contextas used in general to convey that an item, term, etc. may be either X, Yor Z. Thus, such conjunctive language is not generally intended to implythat certain embodiments require at least one of X, at least one of Yand at least one of Z to each be present.

While certain example embodiments have been described, these embodimentshave been presented by way of example only, and are not intended tolimit the scope of the disclosure. Thus, nothing in the foregoingdescription is intended to imply that any particular element, feature,characteristic, step, module, or block is necessary or indispensable.Indeed, the novel methods and systems described herein may be embodiedin a variety of other forms; furthermore, various omissions,substitutions, and changes in the form of the methods and systemsdescribed herein may be made without departing from the spirit of theinventions disclosed herein. The accompanying claims and theirequivalents are intended to cover such forms or modifications as wouldfall within the scope and spirit of certain of the inventions disclosedherein.

Any process descriptions, elements, or blocks in the flow diagramsdescribed herein and/or depicted in the attached figures should beunderstood as potentially representing modules, segments, or portions ofcode which include one or more executable instructions for implementingspecific logical functions or steps in the process. Alternateimplementations are included within the scope of the embodimentsdescribed herein in which elements or functions may be deleted, executedout of order from that shown or discussed, including substantiallyconcurrently or in reverse order, depending on the functionalityinvolved, as would be understood by those skilled in the art.

It should be emphasized that many variations and modifications may bemade to the above-described embodiments, the elements of which are to beunderstood as being among other acceptable examples. All suchmodifications and variations are intended to be included herein withinthe scope of this disclosure. The foregoing description details certainembodiments of the invention. It will be appreciated, however, that nomatter how detailed the foregoing appears in text, the invention can bepracticed in many ways. As is also stated above, it should be noted thatthe use of particular terminology when describing certain features oraspects of the invention should not be taken to imply that theterminology is being re-defined herein to be restricted to including anyspecific characteristics of the features or aspects of the inventionwith which that terminology is associated.

What is claimed is:
 1. A system comprising one or more processors, and anon-transitory computer-readable medium including one or more sequencesof instructions that, when executed by the one or more processors, causethe system to perform the operations comprising: navigating an unmannedaerial vehicle (UAV); periodically monitoring radio frequency (RF)signals external to the UAV; determining a received signal strengthindication (RSSI) value for the monitored RF signals at a plurality ofgeospatial locations during the navigation of the UAV; and storing aplurality of RSSI values and the respective geospatial locations ofwhere a corresponding value was monitored.
 2. The system of claim 1, theoperations further comprising: adjusting navigation of the UAV system tolocations where the determined RSSI value of the monitored signalsremains below a threshold RSSI value.
 3. The system of claim 1, theoperations further comprising: preventing navigation of the UAV to aposition of a stored geospatial location based on the correspondingstored RSSI value.
 4. The system of claim 1, the operations furthercomprising: obtaining a received signal strength indication (RSSI) mapcorresponding to an area around a target object; and dynamicallyadjusting flight of the UAV to avoid areas of particular RSSI values asindicated in the RSSI map.
 5. The system of claim 1, the operationsfurther comprising: generating an RSSI map for RF signals for an areasurrounding a structure.
 6. The system of claim 1, the operationsfurther comprising: based on the plurality of RSSI values and therespective geospatial locations, determining the shape of an RF signallobe generated by an RF transmitter coupled to a structure.
 7. Thesystem of claim 1, the operations further comprising: based on theplurality of RSSI values and the respective geospatial locations,determining whether an RF transmitter coupled to a structure is aimed ina particular direction or azimuth.
 8. The system of claim 1, theoperations further comprising: determining whether an RF transmittercoupled to a structure is operating at a particular frequency or powerlevel.
 9. The system of claim 1, the operations further comprising:based on the plurality of RSSI values and the respective geospatiallocations, determining an orientation of an RF transmitter coupled to astructure.
 10. The system of claim 1, the operations further comprising:receiving RF signals from RF transmitters coupled to two differentstructures.
 11. A method implemented by a system comprising one or moreprocessors, the method comprising: navigating an unmanned aerial vehicle(UAV); periodically monitoring radio frequency (RF) signals external tothe UAV; determining a received signal strength indication (RSSI) valuefor the monitored RF signals at a plurality of geospatial locationsduring the navigation of the UAV; and storing a plurality of RSSI valuesand the respective geospatial locations of where the corresponding valuewas monitored.
 12. The method of claim 1, further comprising: adjustingnavigation of the UAV system to locations where the determined RSSIvalue of the monitored signals remains below a threshold RSSI value. 13.The method of claim 1, further comprising: preventing navigation of theUAV to a position of a stored geospatial location based on thecorresponding stored RSSI value.
 14. The method of claim 1, furthercomprising: obtaining a received signal strength indication (RSSI) mapcorresponding to an area around a target object; and dynamicallyadjusting flight of the UAV to avoid areas of particular RSSI values asindicated in the RSSI map.
 15. The method of claim 1, furthercomprising: generating an RSSI map for RF signals for an areasurrounding a structure.
 16. The method of claim 1, further comprising:based on the plurality of RSSI values and the respective geospatiallocations, determining the shape of an RF signal lobe generated by an RFtransmitter coupled to a structure.
 17. The method of claim 1, furthercomprising: based on the plurality of RSSI values and the respectivegeospatial locations, determining whether an RF transmitter coupled to astructure is aimed in a particular direction or azimuth.
 18. The methodof claim 1, further comprising: determining whether an RF transmittercoupled to a structure is operating at a particular frequency or powerlevel.
 19. The method of claim 1, further comprising: based on theplurality of RSSI values and the respective geospatial locations,determining an orientation of an RF transmitter coupled to a structure.20. The method of claim 1, further comprising: receiving RF signals fromRF transmitters coupled to two different structures.
 21. Anon-transitory computer storage medium comprising instructions that whenexecuted by a system comprising one or more processors, cause the one ormore processors to perform operations comprising: navigating an unmannedaerial vehicle (UAV); periodically monitoring radio frequency (RF)signals external to the UAV; determining a received signal strengthindication (RSSI) value for the monitored RF signals at a plurality ofgeospatial locations during the navigation of the UAV; and storing aplurality of RSSI values and the respective geospatial locations ofwhere the corresponding value was monitored.
 22. The non-transitorycomputer storage medium of claim 1, the operations further comprising:adjusting navigation of the UAV system to locations where the determinedRSSI value of the monitored signals remains below a threshold RSSIvalue.
 23. The non-transitory computer storage medium of claim 1, theoperations further comprising: preventing navigation of the UAV to aposition of a stored geospatial location based on the correspondingstored RSSI value.
 24. The non-transitory computer storage medium ofclaim 1, the operations further comprising: obtaining a received signalstrength indication (RSSI) map corresponding to an area around a targetobject; and dynamically adjusting flight of the UAV to avoid areas ofparticular RSSI values as indicated in the RSSI map.
 25. Thenon-transitory computer storage medium of claim 1, the operationsfurther comprising: generating an RSSI map for RF signals for an areasurrounding a structure.
 26. The non-transitory computer storage mediumof claim 1, the operations further comprising: based on the plurality ofRSSI values and the respective geospatial locations, determining theshape of an RF signal lobe generated by an RF transmitter coupled to astructure.
 27. The non-transitory computer storage medium of claim 1,the operations further comprising: based on the plurality of RSSI valuesand the respective geospatial locations, determining whether an RFtransmitter coupled to a structure is aimed in a particular direction orazimuth.
 28. The non-transitory computer storage medium of claim 1, theoperations further comprising: determining whether an RF transmittercoupled to a structure is operating at a particular frequency or powerlevel.
 29. The non-transitory computer storage medium of claim 1, theoperations further comprising: based on the plurality of RSSI values andthe respective geospatial locations, determining an orientation of an RFtransmitter coupled to a structure.
 30. The non-transitory computerstorage medium of claim 1, the operations further comprising: receivingRF signals from RF transmitters coupled to two different structures.